dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-48811

MEDIUM · 6.7 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing support for integrity check in Windows Virtualization-Based Security (VBS) Enclave allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A missing integrity check in Windows Virtualization-Based Security (VBS) Enclave allows a locally authorized attacker to manipulate enclave memory or code without detection, enabling privilege escalation to higher integrity levels.

MitigationApply Microsoft security updates when available; until then, minimize local attack surface by restricting administrative access and monitoring for suspicious enclave-related activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Run 'winver' or 'systeminfo' and note the OS Build number shown (e.g., 19045.6093 for Win10 22h2)
    Affected if The build number is lower than the version-specific threshold for your Windows release as listed in the affected products
  2. Identify exact Windows release
    Run 'winver' to confirm whether you are on Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2
    Affected if Your identified Windows release and build combination falls below the version-specific threshold in the CVE affected list
  3. Verify VBS Enclave is enabled
    Run 'systeminfo' or open 'msinfo32' and look for the 'Virtualization-Based Security' line under 'Device Security Information'; a value of 'Running' indicates VBS is active
    Affected if Virtualization-Based Security shows as 'Running' or enabled on your system
  4. Check VBS Enclave status via registry
    Check registry key 'HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard' for value 'EnableVirtualizationBasedSecurity' (DWORD = 1 means enabled)
    Affected if The registry value is set to 1 indicating VBS is enabled, which is required for this vulnerability to be exploitable

You are affected if your Windows build is below the version-specific threshold AND VBS Enclave is enabled on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply Microsoft security updates when available; until then, minimize local attack surface by restricting administrative access and monitoring for suspicious enclave-related activity.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21073+ | Windows 10 1607: 10.0.14393.8246+ | Windows 10 1809: 10.0.17763.7558+ | Windows 10 21h2: 10.0.19044.6093+ | Windows 10 22h2: 10.0.19045.6093+ | Windows 11 22h2: 10.0.22621.5624+ | Windows 11 23h2: 10.0.22631.5624+ | Windows 11 24h2: 10.0.26100.4652+

  1. 1. Identify the current Windows version and build by running 'winver' or 'systeminfo' from command prompt
  2. 2. Determine which Windows 10 or 11 version/edition is installed (1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2)
  3. 3. Navigate to Windows Update settings (Settings > Update & Security > Windows Update)
  4. 4. Check for updates and install all available security updates
  5. 5. Alternatively, download and install the specific monthly security update from the Microsoft Update Catalog matching the KB for this CVE (typically released in the month of the CVE publication)
  6. 6. Restart the system after updates are installed
  7. 7. Verify the build number matches or exceeds the fixed version for your Windows edition using 'winver'
Caveat Standard Windows security update with no expected breaking changes; as a local privilege escalation fix, this update may affect VBS enclave behavior for authorized scenarios

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48811 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48811 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data