••••••••••••••••••••
🎯 CVE-2026-45585 🇪🇺 EUVD
💬 0 Diskussion 📄 .md Alle CVEs anzeigen ✕
Social ReaktionenReagiere als Erste:r — dein Feedback zählt!

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? Micr

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.

Klassifikation & Betroffenheit:
CWE-77 Microsoft Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655Windows Server 2025 10.0.26100.0 <10.0.26100.32995Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995microsoft windows_11_24h2 *microsoft windows_11_25h2 *microsoft windows_11_26h1 *
Improper Neutralization of Special Elements used in a Command 🎯 High

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.

🛡️ Empfohlene Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.
Vollständige Definition bei MITRE ➔
🧪 Exploit-Evidenz:
🇩🇪 BSI-Sicherheitshinweise: BSI · mittel · Microsoft Windows 11 und Windows Server 2025: Schwachstelle ermöglicht ↗
📚 Referenzen & Quellen:
Ausnutzungs-Zeitleiste:
CVSS-Vektor-Analyse: 6.8
AV · Angriffsvektor Physisch
AC · Komplexität Gering
PR · Privilegien Keine
UI · Interaktion Keine
S · Scope Unverändert
C · Vertraulichkeit Hoch
I · Integrität Hoch
A · Verfügbarkeit Hoch
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
CNA-Bewertung (microsoft): 6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E…
Veröffentlicht:20.05.2026
Aktualisiert:24.07.2026 09:10
Assigner (CNA):microsoft
EUVD-ID:EUVD-2026-31006
Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache
CWE-77 ✓ Offizieller Patch / Advisory verfügbar
💡 Gegenmaßnahme: Patch-Tuesday Update einspielen oder betroffene Dienste in Windows Defender isolieren.
👁 Sichtung melden

Du hast diese Schwachstelle in deiner Umgebung beobachtet (oder einen Fehlalarm erkannt)? Melde es — nach redaktioneller Freigabe zählt deine Meldung in den Sighting-Vertrauensscore.

🔴 Live Security Advisory & EPSS Exploit Radar

Zero-Day & Vulnerability Intelligence Hub

Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.

90k+ 🇪🇺 EUVD-Datenbank
0 🔴 Critical im Radar
0 ⚠️ CISA KEV
0 🔓 Aktiv ausgenutzt
0 🧪 PoC verfügbar
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
🔴 Criticals pro Monat (12 M) 2025-12: 426 Criticals, davon 9 KEV, Ø CVSS 9,6 Dez 25 2026-01: 433 Criticals, davon 10 KEV, Ø CVSS 9,6 2026-02: 419 Criticals, davon 4 KEV, Ø CVSS 9,5 Feb 26 2026-03: 652 Criticals, davon 6 KEV, Ø CVSS 9,5 2026-04: 578 Criticals, davon 5 KEV, Ø CVSS 9,5 Apr 26 2026-05: 683 Criticals, davon 13 KEV, Ø CVSS 9,5 2026-06: 944 Criticals, davon 14 KEV, Ø CVSS 9,6 Jun 26 2026-07: 1329 Criticals, davon 12 KEV, Ø CVSS 9,6 2026-08: 1830 Criticals, davon 11 KEV, Ø CVSS 9,5 Aug 26 2026-09: 1552 Criticals, davon 17 KEV, Ø CVSS 9,5 2026-10: 1314 Criticals, davon 8 KEV, Ø CVSS 9,5 Okt 26 2026-11: 55 Criticals, davon 0 KEV, Ø CVSS 9,5 Ø CVSS je Monat 10.215 Criticals · ▮ KEV-Anteil · ┄ Ø CVSS 9,5
🏢 Top-Vendor-Veröffentlichungen (6 M) Adobe Apache Software Foundation Apple Google IBM Linux Microsoft Oracle Corporation
● Adobe ● Apache Software Foundation ● Apple ● Google ● IBM ● Linux ● Microsoft ● Oracle Corporation
📈 EPSS-Verteilung (Messungen)
TierCVEsAnteil
≥90 %7850,2 %
≥50 %3.5570,9 %
≥10 %13.1393,2 %
<10 %391.19395,7 %
408.674 CVEs mit EPSS-Score (FIRST.org) · Stand 07.11.2026
Datenquellen & Methodik: Primärquelle ist die EUVD der ENISA (laufender Datenbank-Sync, alle 15 Minuten), abgeglichen mit dem CISA-KEV-Katalog und der NVD — Detail-Dossiers reichern fehlende Felder live per NVD an — mit Fallback auf CIRCL vulnerability-lookup (EU/Non-Profit, aggregiert CVE-, GitHub- und OSV-Advisories). Der CISA-KEV-Katalog (Known Exploited Vulnerabilities, ~1.700 aktiv ausgenutzte Schwachstellen) wird bei jedem Sync vollständig neu geladen und kreuzreferenziert — filterbar über die KEV-Pille. CVSS 3.1 wird nach Ampel-Logik aus Verteidigersicht dekodiert; EPSS bezeichnet die 30-Tage-Exploit-Wahrscheinlichkeit (FIRST.org).
🇪🇺 ENISA EUVD 🇺🇸 NVD ⚠️ CISA KEV ⚡ EPSS
Ökosystem & Hersteller Bedrohungs-Matrix:
Schweregrad & Status:
Hersteller (Datenbank-weit, 110.407 Einträge):
Zeitfenster:
Quelle:
🔍
6.8 MEDIUM
EPSS 1.9%
CVE-2026-45585 👤 Physisch 🔓 Keine Authentifizierung nötig
Microsoft

CVE-2026-45585 | 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? Micr

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

CWE-77 ✓ Offizieller Patch / Advisory verfügbar
💡 Gegenmaßnahme: Patch-Tuesday Update einspielen oder betroffene Dienste in Windows Defender isolieren.
1 von ~1 Einträgen geladen Ende der Trefferliste — 1 Einträge geladen. Tipp: Filter leichtern für tieferes Blättern.