The kernel in Microsoft Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, and Windows 10 allows physically…

published 2015-10-14 11y ago modified 2026-06-17 4mo ago also EUVD-2015-2645

cvss: 7.2; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

The kernel in Microsoft Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, and Windows 10 allows physically proximate attackers to bypass the Trusted Boot protection mechanism, and consequently interfere with the integrity of code, BitLocker, Device Encryption, and Device Health Attestation, via a crafted Boot Configuration Data (BCD) setting, aka "Trusted Boot Security Feature Bypass Vulnerability."

Patch / fix

links 1

docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-111 advisory

Is CVE-2015-2552 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

packetstormsecurity.com http://packetstormsecurity.com/files/133962/Microsoft-Trusted-Boot-Security-Feature-Bypass.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-254 7PK - Security Features

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2015/ms15-111
vendor-advisory, patch
packetstormsecurity.com /files/133962/Microsoft-Trusted-Boot-Security-Feature-Bypass.html
exploit, third-party-advisory, vdb-entry
securitytracker.com /id/1033805
vdb-entry, third-party-advisory
securityfocus.com /archive/1/536678/100/0/threaded
mailing-list, third-party-advisory, vdb-entry

Sources

CVE List CVE-2015-2552
NVD CVE-2015-2552

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.