CVE-2026-45585

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2026-05-20. a secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
6.8
EG Score
6.8(medium)
EG Risk
47(Track*)
EG Risk 47/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
69%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated May 20, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585

Vendor Advisories for CVE-2026-45585(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 131 total refreshes for this CVE.

  1. 2026-07-28 15:36 UTCEPSS rescore
  2. 2026-07-27 14:13 UTCEPSS rescore
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 08:17 UTCEG score recompute
  6. 2026-07-26 08:17 UTCVendor advisory
  7. 2026-07-26 08:17 UTCGHSA enrichment
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:16 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-13 22:30 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 75 more
  1. 2026-07-08 15:16 UTCEPSS rescore
  2. 2026-07-07 13:46 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:07 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 20:33 UTCVendor advisory
  10. 2026-06-29 20:33 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 21:34 UTCVendor advisory
  17. 2026-06-27 21:34 UTCGHSA enrichment
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-26 19:41 UTCVendor advisory
  20. 2026-06-26 19:41 UTCGHSA enrichment
  21. 2026-06-25 16:25 UTCVendor advisory
  22. 2026-06-25 16:25 UTCGHSA enrichment
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
  26. 2026-06-23 21:33 UTCEPSS rescore
  27. 2026-06-22 14:25 UTCEPSS rescore
  28. 2026-06-22 14:25 UTCEPSS rescore
  29. 2026-06-21 14:56 UTCEPSS rescore
  30. 2026-06-21 14:56 UTCEPSS rescore
  31. 2026-06-21 01:59 UTCEPSS rescore
  32. 2026-06-19 19:25 UTCEPSS rescore
  33. 2026-06-18 17:52 UTCEPSS rescore
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-17 17:53 UTCEPSS rescore
  36. 2026-06-17 13:08 UTCGHSA enrichment
  37. 2026-06-16 17:52 UTCEPSS rescore
  38. 2026-06-16 10:48 UTCVendor advisory
  39. 2026-06-16 10:48 UTCGHSA enrichment
  40. 2026-06-15 17:49 UTCEPSS rescore
  41. 2026-06-15 07:51 UTCVendor advisory
  42. 2026-06-15 07:51 UTCGHSA enrichment
  43. 2026-06-14 05:31 UTCVendor advisory
  44. 2026-06-14 05:30 UTCGHSA enrichment
  45. 2026-06-13 23:00 UTCEPSS rescore
  46. 2026-06-13 03:36 UTCVendor advisory
  47. 2026-06-13 03:36 UTCGHSA enrichment
  48. 2026-06-12 23:12 UTCEPSS rescore
  49. 2026-06-12 23:12 UTCEPSS rescore
  50. 2026-06-12 01:20 UTCVendor advisory
  51. 2026-06-12 01:20 UTCGHSA enrichment
  52. 2026-06-11 14:00 UTCEPSS rescore
  53. 2026-06-10 23:26 UTCVendor advisory
  54. 2026-06-10 23:26 UTCGHSA enrichment
  55. 2026-06-10 22:18 UTCEPSS rescore
  56. 2026-06-10 13:22 UTCEPSS rescore
  57. 2026-06-10 13:22 UTCEPSS rescore
  58. 2026-06-09 21:33 UTCVendor advisory
  59. 2026-06-09 21:32 UTCGHSA enrichment
  60. 2026-06-08 19:30 UTCVendor advisory
  61. 2026-06-08 19:30 UTCGHSA enrichment
  62. 2026-06-08 14:17 UTCEPSS rescore
  63. 2026-06-08 14:17 UTCEPSS rescore
  64. 2026-06-07 15:25 UTCEPSS rescore
  65. 2026-06-07 15:25 UTCEPSS rescore
  66. 2026-06-07 14:25 UTCVendor advisory
  67. 2026-06-07 14:25 UTCGHSA enrichment
  68. 2026-06-06 13:47 UTCEPSS rescore
  69. 2026-06-06 13:47 UTCEPSS rescore
  70. 2026-06-06 12:31 UTCVendor advisory
  71. 2026-06-06 12:31 UTCGHSA enrichment
  72. 2026-06-05 22:47 UTCEPSS rescore
  73. 2026-06-05 10:37 UTCVendor advisory
  74. 2026-06-05 10:37 UTCGHSA enrichment
  75. 2026-06-05 06:10 UTCEPSS rescore

Publicly available exploits

(9 references)

Working exploit code is in the public domain (9 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCyellowkey-exploit/YellowKey-Bitlocker
    First seen Jul 23, 2026

    YellowKey free tool for the CVE-2026-45585 BitLocker bypass vulnerability on Windows 10/11. Covered on Tom's Hardware: extract recovery keys, apply remediation, test bypass mitigation and manage BitLocker encryption state. Download YellowKey

    Open source ↗
  • GitHub PoCyellowkeys/YellowKey-Bitlocker-CVE-2026-45585
    First seen Jul 20, 2026

    YellowKey BitLocker CVE-2026-45585 is an open-source utility to extract, backup, and organize BitLocker recovery keys on Windows encrypted drives. Automate volume decryption, manage drive encryption states via command-line tools, export secure configuration files, and track recovery key logs. Download direct repository setup files.

    Open source ↗
  • GitHub PoCyellowkey-bitlocker/YellowKey-Bitlocker
    First seen Jul 19, 2026

    Yellowkey bitlocker CVE-2026-45585 provides an open-source utility manager to extract, backup, and organize BitLocker recovery keys on Windows drives. Automate volume decryption logs, manage drive encryption states via command-line tools, and export secure configuration files directly to GitHub.

    Open source ↗
  • GitHub PoCyellow-key/yellowkey-bitlocker
    First seen Jul 9, 2026

    yellow key bitlocker yellow screen bitlocker bitlocker recovery key CVE-2026-45585 microsoft account secure boot bypass command prompt windows 11 windows 10 surface pro uefi firmware encryption key data recovery troubleshoot boot loop cmd unlock drive setup guide tutorial

    Open source ↗
  • GitHub PoCDesireeontrial76/yellowkey-bitlocker
    First seen Jun 16, 2026

    Manage and recover BitLocker encrypted drives with this tool for Windows 11 recovery key management and educational study of CVE-2026-45585.

    Open source ↗
  • GitHub PoCiDesignStudioz/yellowkey-bitlocker
    First seen Jun 12, 2026

    yellowkey bitlocker github cve download recovery key cve-2026-45585 nightmare-eclipse bypass tpm sniffing decryption tool setup guide tutorial windows 11 windows 10 error fix latest version 2026

    Open source ↗
  • GitHub PoCMysticMite92/yellowkey-bitlocker-544
    First seen Jun 6, 2026

    yellowkey bitlocker github vulnerability bypass cve-2026-45585 windows 11 security zero day exploit winre recovery mode poc nightmare eclipse chaotic eclipse exploit tool usb attack encryption hack script mitigation guide fstx winpeshl shell unpatched fix tool

    Open source ↗
  • GitHub PoCandrei-majer/bitlocker-hardening
    First seen May 24, 2026

    BitLocker TPM+PIN Hardening Against CVE-2026-45585 (YellowKey)

    Open source ↗
  • GitHub PoCMclisterjoeh2o/yellowkey-bitlocker
    First seen May 23, 2026

    yellowkey bitlocker github vulnerability bypass cve-2026-45585 windows 11 security zero day exploit winre recovery mode poc nightmare eclipse chaotic eclipse exploit tool usb attack encryption hack script mitigation guide fstx winpeshl shell unpatched fix tool

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45585?
CVE-2026-45585 is a medium vulnerability published on May 20, 2026. 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…
When was CVE-2026-45585 disclosed?
CVE-2026-45585 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45585 actively exploited?
CVE-2026-45585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 31.2% of all scored CVEs.
What is the CVSS score of CVE-2026-45585?
CVE-2026-45585 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-45585?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45585, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45585

Explore →

Is Your Infrastructure Affected by CVE-2026-45585?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs