nday
CVE-2026-45585

Windows BitLocker Security Feature Bypass Vulnerability

Microsoft / Windows 11 Version 24H2, Windows 11 Version 25H2, Windows 11 version 26H1, Windows Server 2025, Windows Server 2025 (Server Core installation)

CVE 공개: . nday가 아직 패치 근거를 수집하지 않았습니다. 패치가 없다는 뜻은 아닙니다. PoC 출처 4곳 모두 미등재. CISA KEV 미등재.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

command injection
CWE-77, stated by the CNA microsoft 및 NVD, republishing [email protected]
physical
AV:P in 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 (CVSS 3.1) from the CNA microsoft
no authentication required
PR:N in 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 (CVSS 3.1) from the CNA microsoft
no user interaction
UI:N in 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 (CVSS 3.1) from the CNA microsoft
Windows
affected products in the CVE record: Microsoft · Windows 11 Version 24H2, Microsoft · Windows 11 Version 25H2, Microsoft · Windows 11 version 26H1CPE names NVD's analysts give as vulnerable: o:microsoft:windows_11_24h2, o:microsoft:windows_11_25h2, o:microsoft:windows_11_26h1
Windows Server
affected products in the CVE record: Microsoft · Windows Server 2025, Microsoft · Windows Server 2025 (Server Core installation)CPE names NVD's analysts give as vulnerable: o:microsoft:windows_server_2025
operating system
affected products in the CVE record: Microsoft · Windows 11 Version 24H2, Microsoft · Windows 11 Version 25H2, Microsoft · Windows 11 version 26H1, Microsoft · Windows Server 2025, Microsoft · Windows Server 2025 (Server Core installation)CPE names NVD's analysts give as vulnerable: o:microsoft:windows_11_24h2, o:microsoft:windows_11_25h2, o:microsoft:windows_11_26h1, o:microsoft:windows_server_2025the product type of Windows 및 Windows Server in nday's product registry
현재 단계
DIS
공개
CVSS
6.8 MEDIUM v3.1

생명주기

가로축 UTC. 점 = 분 단위, 넓은 막대 = 날짜만, 빈 표시 = 불명 또는 추정.
시점 알 수 없음
DIS공개
05-19T23:30Z
PAT패치
아직 기록 없음
ANA분석
아직 기록 없음
POCPoC
아직 기록 없음
ITW악용
아직 기록 없음
KEVKEV
아직 기록 없음

요약

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:P
Physical: needs physical access to the device
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA microsoft.

이벤트 로그

+DISCVE 공개

CVE 레코드 공개(CNA: microsoft). CVSS 6.8(중간). CISA SSVC 평가상 악용 상태: poc.

출처 cvelist · nday 일괄 수집 · 원본
{
  "id": 425827,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-45585",
  "occurred_at": "2026-05-19T23:30:26.247Z",
  "observed_at": "2026-11-13T05:39:50.021609Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "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",
      "version": "3.1",
      "base_score": 6.8,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2026-05-20T00:00:00+00:00",
      "automatable": "no",
      "exploitation": "poc",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-05-19T23:30:26.247Z",
    "assigner_short_name": "microsoft"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

연구자 논의

최근 7일간 연구자 0명이 언급

목록의 연구자가 X에서 이 CVE를 언급한 게시물입니다. 원문 그대로 보여 주며 nday는 검증하지 않습니다.

명단의 연구자가 X에서 이 CVE를 언급한 게시물은 아직 수집되지 않았습니다.

Discussion

0 comments

No comments yet.