vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2025-48804

Windows BitLocker Security Feature Bypass Vulnerability

MEDIUM
6.8
CVSS Score
Published: July 8, 2025 at 04:57 PM UTC
Updated: June 17, 2026 at 09:30 AM UTC
15 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM6.8
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

Acceptance of extraneous untrusted data with trusted data in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Windows 10 1507· Microsoft
95%
v < 10.0.10240.2107310.0.10240.0 ≤ v < 10.0.10240.2107310.0.10240.0
Affected range stops below 10.0.10240.21073, so it looks safe — our inference, not a vendor statement
Windows 10 1607· Microsoft
95%
v < 10.0.14393.824610.0.14393.0 ≤ v < 10.0.14393.824610.0.14393.0
Affected range stops below 10.0.14393.8246, so it looks safe — our inference, not a vendor statement
Windows 10 1809· Microsoft
95%
v < 10.0.17763.755810.0.17763.0 ≤ v < 10.0.17763.755810.0.17763.0
Affected range stops below 10.0.17763.7558, so it looks safe — our inference, not a vendor statement
Windows 10 21H2· Microsoft
95%
v < 10.0.19044.609310.0.19044.0 ≤ v < 10.0.19044.609310.0.19044.0
Affected range stops below 10.0.19044.6093, so it looks safe — our inference, not a vendor statement
Windows 10 22H2· Microsoft
95%
v < 10.0.19045.609310.0.19045.0 ≤ v < 10.0.19045.609310.0.19045.0
Affected range stops below 10.0.19045.6093, so it looks safe — our inference, not a vendor statement
Windows 11 22H2· Microsoft
95%
v < 10.0.22621.562410.0.22621.0 ≤ v < 10.0.22621.562410.0.22621.0
Affected range stops below 10.0.22621.5624, so it looks safe — our inference, not a vendor statement
Windows 11 23H2· Microsoft
95%
v < 10.0.22631.562410.0.22631.0 ≤ v < 10.0.22631.562410.0.22631.0
Affected range stops below 10.0.22631.5624, so it looks safe — our inference, not a vendor statement
Windows 11 24H2· Microsoft
95%
v < 10.0.26100.465210.0.26100.0 ≤ v < 10.0.26100.465210.0.26100.0
Affected range stops below 10.0.26100.4652, so it looks safe — our inference, not a vendor statement
Windows Server 2012· Microsoft
95%
6.2.9200.0 ≤ v < 6.2.9200.255736.3.9600.0 ≤ v < 6.3.9600.226766.2.9200.06.3.9600.0r2
Affected range stops below 6.2.9200.25573, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.3.9600.22676, so it looks safe — our inference, not a vendor statement
Windows Server 2016· Microsoft
95%
v < 10.0.14393.824610.0.14393.0 ≤ v < 10.0.14393.824610.0.14393.0
Affected range stops below 10.0.14393.8246, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor AdvisoryPatch
Source: [email protected]
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-48804

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.8MEDIUMmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-349

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card