CVERadar
MEDIUM · CVSS 3.1 6.8Public PoCEPSS 0.65% (p51)Threat level 38

CVE-2025-48804: CVE-2025-48804: Acceptance of extraneous untrusted data with trusted data in Windows BitLocker allows an u…

microsoft · windows 10 1507 · NVD published 2025-07-08 · posted 2026-04-30 · last modified 2026-06-17

What it is

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

WeaknessCWE-349
CVSS vectorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (source: [email protected])
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2026-04-30 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

1 public repositories from 1 accounts, first seen 2026-04-30. Most starred: garatc/BitUnlocker (245 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

  • microsoft windows 10 1507: upgrade to 10.0.10240.21073 or later
  • microsoft windows 10 1607: upgrade to 10.0.14393.8246 or later
  • microsoft windows 10 1809: upgrade to 10.0.17763.7558 or later
  • microsoft windows 10 21h2: upgrade to 10.0.19044.6093 or later
  • microsoft windows 10 22h2: upgrade to 10.0.19045.6093 or later
  • microsoft windows 11 22h2: upgrade to 10.0.22621.5624 or later
  • microsoft windows 11 23h2: upgrade to 10.0.22631.5624 or later
  • microsoft windows 11 24h2: upgrade to 10.0.26100.4652 or later
  • microsoft windows server 2016: upgrade to 10.0.14393.8246 or later
  • microsoft windows server 2019: upgrade to 10.0.17763.7558 or later
  • microsoft windows server 2022: upgrade to 10.0.20348.3932 or later
  • microsoft windows server 2022 23h2: upgrade to 10.0.25398.1732 or later
  • microsoft windows server 2025: upgrade to 10.0.26100.4652 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources