Security readout for executives and security teams
Plain-English summary
YellowKey can bypass BitLocker protections on affected Windows systems when an attacker has physical access. A stolen or unattended device could expose sensitive data despite disk encryption. The supplied evidence rates it medium, but consequences may be severe for mobile devices containing valuable information.
Executive priority
Treat this as a prompt, targeted physical-security and data-protection issue. Prioritize high-value laptops and other devices at risk of loss or theft; broad emergency disruption is not supported by the supplied evidence.
Technical view
CVE-2026-45585 is a BitLocker security-feature bypass affecting specified Windows 11 and Windows Server builds. Its CVSS 3.1 score is 6.8, requiring physical access but no privileges or user interaction. Microsoft identifies CWE-77 and states TPM+PIN configurations are not exploitable.
Likely exposure
Affected Windows 11 24H2, 25H2, 26H1, and Windows Server 2025 systems may be exposed, particularly portable or physically accessible devices without TPM+PIN. The supplied bundle does not identify other versions as affected.
Exploitation context
Proof-of-concept material is public, increasing the likelihood of attempted exploitation. The CVSS vector requires physical access. The supplied bundle does not report active exploitation, and the CVE is not listed as KEV.
Researcher notes
Public proof of concept and physical attack requirements are supported, but the bundle does not describe the bypass mechanics or report real-world exploitation. Temporary mitigation details are absent, so implementation should follow Microsoft’s advisory directly. No offensive reproduction is necessary for exposure validation.
Mitigation direction
- Review Microsoft’s advisory and apply its current temporary mitigation guidance.
- Prioritize devices used at home, during travel, or otherwise vulnerable to theft.
- Confirm whether exposed devices use TPM+PIN, which Microsoft states prevents exploitation.
- Install Microsoft’s security update when the advisory confirms availability.
Validation and detection
- Inventory affected Windows editions, versions, and build numbers.
- Identify BitLocker authentication configurations and verify TPM+PIN deployment where expected.
- Prioritize physically accessible, portable, and travel-assigned devices for review.
- Recheck Microsoft’s advisory for updated mitigation and security-update status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-45585 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: 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 and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:C0.95.9microsoftVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows BitLocker Security Feature Bypass VulnerabilityCVE reference, microsoft · vendor-advisory, patch
- https://github.com/Nightmare-Eclipse/YellowKeyCVE reference, CISA-ADP · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.