Skip to content
Noroxi
NVD / CVE Program· CNA microsoft

CVE-2026-45585: Windows BitLocker Security Feature Bypass Vulnerability

Noroxi assessment

Priority: Monitor (action score 28/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.7% of all records.
  • Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655; Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655; Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269.

Low priority for now. Upgrade to Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655; Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655; Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.8 · v3.1—Proof of concept Fix available
Published
May 19, 2026
Updated
Aug 10, 2026
EPSS
1.8% · 79th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · microsoft
6.8
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-45585

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for microsoft records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
microsoftwindows 11 24h2
microsoftwindows 11 25h2
microsoftwindows 11 26h1
microsoftwindows server 2025

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • microsoft windows server 2025all versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

  • Microsoft Windows 11 Version 24H2

    • 10.0.26100.0 and later · before 10.0.26100.8655affected

  • Microsoft Windows 11 Version 25H2

    • 10.0.26200.0 and later · before 10.0.26200.8655affected

  • Microsoft Windows 11 version 26H1

    • 10.0.28000.0 and later · before 10.0.28000.2269affected

  • Microsoft Windows Server 2025

    • 10.0.26100.0 and later · before 10.0.26100.32995affected

  • Microsoft Windows Server 2025 (Server Core installation)

    • 10.0.26100.0 and later · before 10.0.26100.32995affected

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-60710Host Process for Windows Tasks Elevation of Privilege VulnerabilityKEV
    62This week
  • CVE-2025-50165Windows Graphics Component Remote Code Execution Vulnerability
    42Plan
  • CVE-2025-21311Windows NTLM V1 Elevation of Privilege Vulnerability
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-42896May 12, 2026 · Windows DWM Core Library Elevation of Privilege Vulnerability
    31Monitor
  • ← EarlierCVE-2026-40369May 12, 2026 · Windows Kernel Elevation of Privilege Vulnerability
    32Monitor
  • Later →CVE-2026-42829Jun 9, 2026 · Windows Administrator Protection Secure Feature Bypass Vulnerability
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Windows 11 Version 24H2 for x64-based Systems10.0.26100.8655 · KB5094126Microsoft (MSRC)
Windows 11 Version 25H2 for x64-based Systems10.0.26200.8655 · KB5094126Microsoft (MSRC)
Windows 11 version 26H1 for x64-based Systems10.0.28000.2269 · KB5095051Microsoft (MSRC)
Windows Server 202510.0.26100.32995 · KB5094125Microsoft (MSRC)
Windows Server 2025 (Server Core installation)10.0.26100.32995 · KB5094125Microsoft (MSRC)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×9

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-05-20
Proof-of-concept repository on GitHubstars:12026-05-21
Proof-of-concept repository on GitHubstars:62026-05-24
Proof-of-concept repository on GitHubstars:12026-05-31
Proof-of-concept repository on GitHubstars:02026-06-04
Proof-of-concept repository on GitHubstars:02026-06-08
Proof-of-concept repository on GitHubstars:02026-08-20
Proof-of-concept repository on GitHubstars:02026-08-24
Proof-of-concept repository on GitHubstars:02026-08-24

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodayNov 11, 2026+175 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5048856 days apartClipboard User Service Elevation of Privilege Vulnerability
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Physical access to the device is required.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records