Skip to content
Fencer Intel
medium 6.1

CVE-2025-55330 json

Windows BitLocker Security Feature Bypass Vulnerability

published last yr. modified 4mo ago also EUVD-2025-34343

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

Summary

Improper enforcement of behavioral workflow in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.

Patch / fix

  • Microsoft Windows 11 version 22H2 10.0.22621.6060
  • Microsoft Windows 11 version 22H3 10.0.22631.6060
  • Microsoft Windows 11 Version 23H2 10.0.22631.6060
  • Microsoft Windows 11 Version 24H2 10.0.26100.6899
  • Microsoft Windows 11 Version 25H2 10.0.26200.6899
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.1913
  • Microsoft Windows Server 2025 10.0.26100.6899
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.6899

Is CVE-2025-55330 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
CNA 3.1 6.1 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 4.6 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Microsoft Windows 11 version 22H2
  • Microsoft Windows 11 version 22H3
  • Microsoft Windows 11 Version 23H2
  • Microsoft Windows 11 Version 24H2
  • Microsoft Windows 11 Version 25H2
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness
  • CWE-841 Improper Enforcement of Behavioral Workflow

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.