dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-47159

HIGH · 7.8 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 →
80/100
Remediation priority · High
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
Protection mechanism failure 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 protection mechanism failure in Windows Virtualization-Based Security (VBS) Enclave allows a local authorized attacker to bypass security controls and elevate privileges. VBS Enclaves use hardware virtualization to create isolated execution environments for protecting sensitive data, and this vulnerability enables an attacker with local access to escape the enclave protection and gain higher-level Windows privileges.

MitigationApply Microsoft security updates for CVE-2025-47159 when released. In the interim, restrict local administrative access and monitor for suspicious processes interacting with VBS Enclave APIs.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 if VBS is enabled on the system
    Run 'systeminfo' from command prompt and look for the 'Virtualization-Based Security' line in the output, or open 'msinfo32' and navigate to the 'Virtualization-Based Security' section
    Affected if VBS is not running or not configured (the vulnerability only affects systems with VBS Enclaves enabled)
  2. Verify VBS Enclave feature status
    Check the Windows Feature settings: run 'Get-WindowsOptionalFeature -Online -FeatureName *VBS*' in PowerShell, or inspect registry key 'HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard' for VBS Enclave configuration
    Affected if VBS Enclave feature is explicitly enabled on the system
  3. Determine installed Windows build number
    Run 'winver' and note the build number shown (e.g., 19045), or run 'systeminfo' and check the 'OS Build' line, or use 'ver' command from command prompt
    Affected if The build number is below the fixed version for your Windows release
  4. Compare against affected version ranges
    Match your Windows release (10 1507, 10 1607, 10 1809, 10 21h2, 10 22h2, 11 22h2, 11 23h2, or 11 24h2) and build number to the affected ranges: 10240.21073, 14393.8246, 17763.7558, 19044.6093, 19045.6093, 22621.5624, 22631.5624, or 26100.4652 respectively
    Affected if Your Windows version and build fall below the specified threshold for your release channel

You are affected only if VBS Enclaves are enabled on your system AND your Windows build number is below the fixed threshold for your specific Windows release version.

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 for CVE-2025-47159 when released. In the interim, restrict local administrative access and monitor for suspicious processes interacting with VBS Enclave APIs.

Recommended fix High confidence

Install the latest Windows Security Update from Microsoft Update that addresses CVE-2025-47159 (check msrc.microsoft.com for the specific KB article number for your Windows version)

  1. 1. Open Windows Settings on the affected system
  2. 2. Navigate to Windows Update (Settings > Update & Security > Windows Update)
  3. 3. Click 'Check for updates' to download and install the latest security updates
  4. 4. Restart the system after updates are installed
  5. 5. Verify the installed Windows version meets or exceeds the fixed build number for your version (e.g., Windows 10 22h2 should be >= 10.0.19045.6093)
Caveat Standard Windows update - ensure backups of critical data exist before applying updates

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47159 — 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-47159 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