Vulnpedia
← All CVEs

CVE-2026-45585

MEDIUM 6.8 ALL-YEARS

Published 2026-05-19 · Last modified 2026-08-10 · microsoft · NVD: Modified

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.

LIMITED SIGNALS

No known exploitation, public exploit, or elevated probability at this time. Track for changes.

Exploitation likelihood

1.9%chance of exploitation in 30 days · 79th percentile

○ In CISA KEV○ Catalogued PoC◆ SSVC: exploitation poc, automatable no

Impact if exploited

6.8CVSS 3.1 · MEDIUM · CNA

  • ConfidentialityHigh
  • IntegrityHigh
  • AvailabilityHigh

What an attacker needs

  • ⚠Access: Requires physical access to the device
  • ✓Privileges: No account or privileges required
  • ✓User interaction: No user interaction needed
  • ✓Complexity: No special conditions — reliably repeatable

✓ lowers the bar for an attacker · ⚠ raises it

Proof of concept

No public PoC is currently catalogued.

Search for new PoCs

Search GitHub now — results may be empty or unverified.

Tracked sources are checked weekly for the full archive, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.

Data snapshot:

Affected

Vendors Microsoft

Products Windows 11 Version 24h2 Windows 11 Version 25h2 Windows 11 Version 26h1 Windows Server 2025 Windows Server 2025 (Server Core Installation) Windows 11 24h2 Windows 11 25h2 Windows 11 26h1

Weakness (CWE)

  • CWE-77: : Improper Neutralization of Special Elements used in a Command ('Command Injection')

CVSS vector

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

References and research data (JSON)

Unverified PoC candidates

Catalogue matches for further research. These repositories have not been validated as working exploits.

12 candidates

Known Affected Software Configurations

VendorProductVersion range
MicrosoftWindows 11 24h2*
MicrosoftWindows 11 25h2*
MicrosoftWindows 11 26h1*
MicrosoftWindows Server 2025*

All CVSS metrics

  • MEDIUM 6.8 v3.1 · CNA Primary
    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
  • MEDIUM 6.8 v3.1 · NVD Secondary
    CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

Exploit-tagged references (not proof of a PoC)

Patches & mitigations

Advisories

Sources: NVD · CVE.org · All sources and attribution · EPSS