Medium Injection exploit reference

CVE-2026-45585 — Windows BitLocker Security Feature Bypass Vulnerability

Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available. Mitigation FAQs Should I leverage the temporary mitigation? Microsoft recommends that you consider implementing these mitigations if you are concerned your devices and data are at risk of being compromised or stolen. For example, if your organization’s employees take their work devices home or on business travel. What impact to service availability/management could be caused by implementing the mitigations? Implementing these mitigations will not impact service availability or management operations. Do customers need to revert the changes made to mitigate the vulnerability once the security update to protect against this vulnerability is available? No. The security update will maintain the mitigation's behavior once the security update is installed. I am using TPM+PIN, am I at risk of this vulnerability being exploited No, if you are using TPM+PIN the vulnerability is not exploitable.

Published May 19, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: microsoft

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.5% (30-day exploitation probability)+6
Technical severity (medium)+3
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.49%

ahead of 41% of scored CVEs · Oct 14, 2026

Affects

Microsoft

Windows 11 24h2 and 7 more

CVSS base

6.8

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented mitigation — msrc.microsoft.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows 11 26h1…).
Apply the documented mitigations until a definitive fix is available.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Microsoft	Windows 11 24h2	versions not specified by the source	Vulnerable	NIST National Vulnerability Database
Microsoft	Windows 11 25h2	versions not specified by the source	Vulnerable	NIST National Vulnerability Database
Microsoft	Windows 11 26h1	versions not specified by the source	Vulnerable	NIST National Vulnerability Database
Microsoft	Windows 11 Version 24H2	≥ 10.0.26100.0 and < 10.0.26100.8655	Vulnerable	CVE Program (cve.org) e CISA ADP
Microsoft	Windows 11 Version 25H2	≥ 10.0.26200.0 and < 10.0.26200.8655	Vulnerable	CVE Program (cve.org) e CISA ADP
Microsoft	Windows 11 version 26H1	≥ 10.0.28000.0 and < 10.0.28000.2269	Vulnerable	CVE Program (cve.org) e CISA ADP
Microsoft	Windows Server 2025	versions not specified by the source	Vulnerable	NIST National Vulnerability Database
Microsoft	Windows Server 2025	≥ 10.0.26100.0 and < 10.0.26100.32995	Vulnerable	CVE Program (cve.org) e CISA ADP
Microsoft	Windows Server 2025 (Server Core installation)	≥ 10.0.26100.0 and < 10.0.26100.32995	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Physical

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.8	CVSS 3.1	Medium	0.9	5.9	secure@microsoft.com via NIST National Vulnerability Database
6.8	CVSS 3.1	Medium	—	—	microsoft via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: secure@microsoft.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-77 · Command Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.49%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Look for parameters with command/query metacharacters and unexpected child processes of the service.

endpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · microsoft/windows 11 version 24h2, microsoft/windows 11 version 25h2, microsoft/windows 11 version 26h1, microsoft/windo
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 6.8
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
May 19, 2026 · microsoft

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585
Mitigation, Vendor Advisory, vendor-advisory, patch, NIST National Vulnerability Database
github.com/Nightmare-Eclipse/YellowKey
Exploit, Third Party Advisory, NIST National Vulnerability Database

Elsewhere on this site

Microsoft
every CVE for this vendor

Injection
same class

CWE-77
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d
Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-45585 is "Windows BitLocker Security Feature Bypass Vulnerability", rated Medium. It affects Windows 11 24h2 (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.8 describes technical severity. EPSS 0.49% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.