CVE-2026-45585

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.8 from GitHub Security Advisory published 2026-05-20. The CNA's CVSS baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-31006 (ENISA EUVD) · GHSA-2h24-8rjh-qgjv (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 6.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.8MEDIUMmedium confidence
EG Risk
47
EG Risk 47/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.9%
EPSS %ILE
79th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 20, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated May 20, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

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 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 270 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 170 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(11 references, 10 shown)

Public exploit code is referenced for this CVE (10 GitHub PoCs), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoCYellowKeyBitLocker-CVE/YellowKey-BitLocker-CVE-2026-45585
    Published Sep 27, 2026

    YellowKey BitLocker recovery audits CVE-2026-45585: yellowkey github, TPM, recovery key backup. Windows 10/11 CLI GUI, portable audit tool for volumes you own. Extract and run. Official free download. Download:➧

    Open source ↗
  • GitHub PoCyellowkeycve2026/YellowKey-BitLocker-CVE-2026-45585
    Published Aug 26, 2026

    YellowKey BitLocker recovery - bitlocker yellowkey, yellowkey bitlocker, CVE-2026-45585, yellowkey github, yellowkey vulnerability, yellowkey CVE, TPM, BitLocker recovery key backup, Windows 10/11, CLI GUI, portable audit tool. Download:🡇

    Open source ↗
  • GitHub checkeryellowkeybitlocker/YellowKey-Bitlocker-CVE-2026-45585
    Published Aug 1, 2026

    YellowKey BitLocker CVE-2026-45585 free open-source utility to extract, backup and view BitLocker recovery keys on Windows 10/11. BitLocker bypass vulnerability tool, remediation and mitigation. Tom's Hardware coverage. Check TPM status, protector types, encryption state. Download YellowKey free, portable, no install needed.

    Open source ↗
  • GitHub PoCyellowkey-exploit/YellowKey-Bitlocker
    Published 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
    Published 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
    Published 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 PoCDesireeontrial76/yellowkey-bitlocker
    Published 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
    Published 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
    Published 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
    Published May 24, 2026

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

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45585?
CVE-2026-45585 is a medium-severity vulnerability; its CVE record was 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 made public?
CVE-2026-45585 was made public on May 19, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on May 20, 2026. EchelonGraph's copy of the record carries a last-modified date of August 10, 2026; the record at its source may have been updated since.
Is CVE-2026-45585 actively exploited?
CVE-2026-45585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45585?
CVE-2026-45585 has a CVSS base score of 6.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-45585?
A fix for CVE-2026-45585 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45585 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs