Skip to main content
VulnerabilityPublished Updated

CVE-2026-45585: Microsoft Windows 11 Version 24H2 · Command Injection

Affects Microsoft Windows 11 Version 24H2Source CVE Database V5

0
Compare

Public exploit available · CVSS 6.8 Medium : upgrade to 10.0.26100.8655 as a priority.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.8% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.0.26100.8655, 10.0.26200.8655, 10.0.28000.2269 +1
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
MicrosoftWindows 11 Version 24H2Affected
  • >=10.0.26100.0 <10.0.26100.8655
Fixed in
  • 10.0.26100.8655
MicrosoftWindows 11 Version 25H2Affected
  • >=10.0.26200.0 <10.0.26200.8655
Fixed in
  • 10.0.26200.8655
MicrosoftWindows 11 version 26H1Affected
  • >=10.0.28000.0 <10.0.28000.2269
Fixed in
  • 10.0.28000.2269
MicrosoftWindows Server 2025Affected
  • >=10.0.26100.0 <10.0.26100.32995
Fixed in
  • 10.0.26100.32995
MicrosoftWindows Server 2025 (Server Core installation)Affected
  • >=10.0.26100.0 <10.0.26100.32995
Fixed in
  • 10.0.26100.32995

AI-suggested

Microsoft recommends implementing the provided mitigation guidance as a temporary workaround until a security update is released. These mitigations do not affect service availability or management operations. Users employing TPM+PIN are not at risk from this vulnerability. Once the official security update is available, it will maintain the mitigation behavior, so no reversion of changes is necessary.

Description

Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as &quot;YellowKey&quot;. 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.

References

Community reviews

Loading reviews…