CVE-2026-45585: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in Microsoft Windows 11 Version 24H2
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.
AI Analysis
Technical Summary
This vulnerability is a command injection flaw in Microsoft Windows 11 Version 24H2 (build 10.0.26100.0) that allows improper neutralization of special elements used in commands, leading to a security feature bypass referred to as "YellowKey." Microsoft has publicly acknowledged the issue and released mitigation guidance as a workaround. The vulnerability has a CVSS 3.1 base score of 6.8, indicating medium severity with potential high impact on confidentiality, integrity, and availability. The vendor advisory confirms no official patch is yet available, but mitigations can be applied without affecting service availability. Use of TPM+PIN protects against exploitation.
Potential Impact
Successful exploitation could lead to compromise of confidentiality, integrity, and availability of affected systems. The vulnerability allows bypassing a security feature, potentially enabling unauthorized command execution. However, exploitation requires local access (AV:P) and no user interaction is needed. Systems using TPM+PIN are not vulnerable. No known exploits are reported in the wild at this time.
Mitigation Recommendations
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. Monitor the Microsoft Security Response Center advisory for updates.
CVE-2026-45585: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in Microsoft Windows 11 Version 24H2
Description
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.
CVSS v3.1
Score 6.8medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability is a command injection flaw in Microsoft Windows 11 Version 24H2 (build 10.0.26100.0) that allows improper neutralization of special elements used in commands, leading to a security feature bypass referred to as "YellowKey." Microsoft has publicly acknowledged the issue and released mitigation guidance as a workaround. The vulnerability has a CVSS 3.1 base score of 6.8, indicating medium severity with potential high impact on confidentiality, integrity, and availability. The vendor advisory confirms no official patch is yet available, but mitigations can be applied without affecting service availability. Use of TPM+PIN protects against exploitation.
Potential Impact
Successful exploitation could lead to compromise of confidentiality, integrity, and availability of affected systems. The vulnerability allows bypassing a security feature, potentially enabling unauthorized command execution. However, exploitation requires local access (AV:P) and no user interaction is needed. Systems using TPM+PIN are not vulnerable. No known exploits are reported in the wild at this time.
Mitigation Recommendations
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. Monitor the Microsoft Security Response Center advisory for updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- microsoft
- Date Reserved
- 2026-05-12T19:55:45.729Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- workaround
- Vendor Advisory Urls
- [{"url":"https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585","vendor":"Microsoft"}]
Threat ID: 6a0cf6e2ba1db47362fb1b52
Added to database: 05/19/2026, 23:48:50 UTC
Last enriched: 08/11/2026, 16:59:07 UTC
Last updated: 08/18/2026, 22:49:27 UTC
Views: 335
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.