CVE-2026-45585
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?
Leer descripción completaMostrar menos
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
- Versión: 3.1
- Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Puntuación base: 6.8
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.49%
- Percentil entre todas las CVEs puntuadas: 40
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (4)
CWE
- CWE-77
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-45585",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-45585",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"version": "2.0.3",
"timestamp": "2026-05-20T00:00:00+00:00"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "secure@microsoft.com",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 6.8,
"attackVector": "PHYSICAL",
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"integrityImpact": "HIGH",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "HIGH",
"privilegesRequired": "NONE",
"confidentialityImpact": "HIGH"
},
"impactScore": 5.9,
"exploitabilityScore": 0.9
}
]
},
"affected": [
{
"source": "secure@microsoft.com",
"affectedData": [
{
"vendor": "Microsoft",
"product": "Windows 11 Version 24H2",
"versions": [
{
"status": "affected",
"version": "10.0.26100.0",
"lessThan": "10.0.26100.8655",
"versionType": "custom"
}
],
"platforms": [
"x64-based Systems"
]
},
{
"vendor": "Microsoft",
"product": "Windows 11 Version 25H2",
"versions": [
{
"status": "affected",
"version": "10.0.26200.0",
"lessThan": "10.0.26200.8655",
"versionType": "custom"
}
],
"platforms": [
"x64-based Systems"
]
},
{
"vendor": "Microsoft",
"product": "Windows 11 version 26H1",
"versions": [
{
"status": "affected",
"version": "10.0.28000.0",
"lessThan": "10.0.28000.2269",
"versionType": "custom"
}
],
"platforms": [
"x64-based Systems"
]
},
{
"vendor": "Microsoft",
"product": "Windows Server 2025",
"versions": [
{
"status": "affected",
"version": "10.0.26100.0",
"lessThan": "10.0.26100.32995",
"versionType": "custom"
}
],
"platforms": [
"x64-based Systems"
]
},
{
"vendor": "Microsoft",
"product": "Windows Server 2025 (Server Core installation)",
"versions": [
{
"status": "affected",
"version": "10.0.26100.0",
"lessThan": "10.0.26100.32995",
"versionType": "custom"
}
],
"platforms": [
"x64-based Systems"
]
}
]
}
],
"published": "2026-05-20T00:16:44.380",
"references": [
{
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"source": "secure@microsoft.com"
},
{
"url": "https://github.com/Nightmare-Eclipse/YellowKey",
"tags": [
"Exploit",
"Third Party Advisory"
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
],
"vulnStatus": "Modified",
"weaknesses": [
{
"type": "Secondary",
"source": "secure@microsoft.com",
"description": [
{
"lang": "en",
"value": "CWE-77"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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.\nWe are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.\nMitigation FAQs\nShould I leverage the temporary mitigation?\nMicrosoft 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.\nWhat impact to service availability/management could be caused by implementing the mitigations?\nImplementing these mitigations will not impact service availability or management operations.\nDo customers need to revert the changes made to mitigate the vulnerability once the security update to protect against this vulnerability is available?\nNo. The security update will maintain the mitigation's behavior once the security update is installed.\nI am using TPM+PIN, am I at risk of this vulnerability being exploited\nNo, if you are using TPM+PIN the vulnerability is not exploitable."
},
{
"lang": "es",
"value": "Microsoft tiene conocimiento de una vulnerabilidad de omisión de característica de seguridad en Windows conocida públicamente como 'YellowKey'. La prueba de concepto para esta vulnerabilidad se ha hecho pública violando las mejores prácticas de vulnerabilidad coordinada.\nEstamos emitiendo este CVE para proporcionar orientación de mitigación que se puede implementar para proteger contra esta vulnerabilidad hasta que la actualización de seguridad esté disponible.\nPreguntas frecuentes sobre mitigación\n¿Debo utilizar la mitigación temporal?\nMicrosoft recomienda que considere implementar estas mitigaciones si le preocupa que sus dispositivos y datos estén en riesgo de ser comprometidos o robados. Por ejemplo, si los empleados de su organización llevan sus dispositivos de trabajo a casa o en viajes de negocios.\n¿Qué impacto en la disponibilidad/gestión del servicio podría ser causado por la implementación de las mitigaciones?\nLa implementación de estas mitigaciones no tendrá impacto en la disponibilidad del servicio o en las operaciones de gestión.\n¿Necesitan los clientes revertir los cambios realizados para mitigar la vulnerabilidad una vez que la actualización de seguridad para proteger contra esta vulnerabilidad esté disponible?\nNo. La actualización de seguridad mantendrá el comportamiento de la mitigación una vez que la actualización de seguridad esté instalada.\nEstoy usando TPM+PIN, ¿estoy en riesgo de que esta vulnerabilidad sea explotada?\nNo, si está usando TPM+PIN la vulnerabilidad no es explotable."
}
],
"lastModified": "2026-07-24T09:10:00.153",
"configurations": [
{
"nodes": [
{
"negate": false,
"cpeMatch": [
{
"criteria": "cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:x64:*",
"vulnerable": true,
"matchCriteriaId": "1799DC19-34BA-42B4-A6DC-02774202DE22"
},
{
"criteria": "cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:x64:*",
"vulnerable": true,
"matchCriteriaId": "AAAB3FDE-4FF2-47DE-9BDA-25B2855054E7"
},
{
"criteria": "cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:x64:*",
"vulnerable": true,
"matchCriteriaId": "DA9F6F61-46D3-4ECD-8B5D-1484222B7364"
},
{
"criteria": "cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "9B12238F-DF99-4247-B645-259C3FD98F61"
}
],
"operator": "OR"
}
]
}
],
"sourceIdentifier": "secure@microsoft.com"
}