---
cve: "CVE-2026-45585"
severity: "MEDIUM"
cvss: 6.8
epss: "1.9%"
vendor: "Microsoft"
kev: false
exploited: false
published: "2026-05-20 00:16:44"
tags: [cve, security, medium]
source: tsecurity.de CVE-Dossier
exported: "2026-11-08T11:30:53+01:00"
---

# CVE-2026-45585

> 6.8 MEDIUM

## Beschreibung

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.

## CNA-Record (Kanon, cvelistV5)

- CNA: **microsoft**
- State: PUBLISHED
- Stand: 2026-08-10 15:13:58
- CNA-CVSS: **6.8** (`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`)

## CISA-Anreicherung (vulnrichment/ADP)

- CISA-SSVC (Coordinator, v2.0.3):
  - Exploitation: **poc**
  - Automatable: **no**
  - Technical Impact: **total**

## CVSS-Vektor

```
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
```

| Metrik | Wert | Bewertung |
|---|---|---|
| AV Angriffsvektor | Physisch | good |
| AC Komplexität | Gering | bad |
| PR Privilegien | Keine | bad |
| UI Interaktion | Keine | bad |
| S Scope | Unverändert | good |
| C Vertraulichkeit | Hoch | bad |
| I Integrität | Hoch | bad |
| A Verfügbarkeit | Hoch | bad |

## Schwachstellen-Klasse

- **CWE-77** — Improper Neutralization of Special Elements used in a Command
  The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

## Angriffsmuster (CAPEC)

- [CAPEC-15 — Command Delimiters](https://capec.mitre.org/data/definitions/15.html) _(Severity: High)_
- [CAPEC-40 — Manipulating Writeable Terminal Devices](https://capec.mitre.org/data/definitions/40.html) _(Severity: Very High)_
- [CAPEC-43 — Exploiting Multiple Input Interpretation Layers](https://capec.mitre.org/data/definitions/43.html) _(Severity: High)_
- [CAPEC-75 — Manipulating Writeable Configuration Files](https://capec.mitre.org/data/definitions/75.html) _(Severity: Very High)_
- [CAPEC-76 — Manipulating Web Input to File System Calls](https://capec.mitre.org/data/definitions/76.html) _(Severity: Very High)_
- [CAPEC-136 — LDAP Injection](https://capec.mitre.org/data/definitions/136.html) _(Severity: High)_
- [CAPEC-183 — IMAP/SMTP Command Injection](https://capec.mitre.org/data/definitions/183.html) _(Severity: Medium)_
- [CAPEC-248 — Command Injection](https://capec.mitre.org/data/definitions/248.html) _(Severity: High)_

## BSI-Hinweise (deutsch)

- [Microsoft Windows 11 und Windows Server 2025: Schwachstelle ermöglicht Umgehen der Laufwerksverschlüsselung](https://wid.cert-bund.de/portal/wid/sicherheitshinweis/WID-SEC-W-2026-1609) — _BSI-Einstufung: mittel_
  Ein Angreifer mit physischem Zugriff kann eine Schwachstelle in Microsoft Windows 11 und Microsoft Windows Server 2025 ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

## Referenzen

- <https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585>
- <https://github.com/Nightmare-Eclipse/YellowKey>

---
_Exportiert aus dem [tsecurity.de CVE-Dossier](https://tsecurity.de/sicherheitsluecken/cve-2026-45585/) · Datenquellen: EUVD (ENISA), NVD, OSV, CISA KEV, FIRST EPSS, Exploit-DB, BSI WID (CSAF)_
