dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-53717

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.22621.6060 / 10.0.26100.6899 or later.
See remediation →
72/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
Reliance on untrusted inputs in a security decision 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

This is a local privilege escalation vulnerability in Windows Virtualization-Based Security (VBS) Enclave. An authorized local attacker can exploit improper validation of untrusted inputs in security decision logic to elevate their privileges to a higher level within the VBS Enclave environment.

MitigationApply the relevant Microsoft Windows security update when available. Verify VBS Enclave functionality remains operational after patching.

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 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899

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

CVSS:3.1/AV:L/AC:H/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 Windows 11 build version
    Run 'winver' or execute 'systeminfo | findstr /C:"OS Version"' to obtain the full build number including the revision portion (e.g., 10.0.22621.6060)
    Affected if The installed build number falls within any of these ranges: 22h2 before 10.0.22621.6060, 23h2 at or below 10.0.22631.6060, 24h2 before 10.0.26100.6899, or 25h2 before 10.0.26200.6899
  2. Confirm VBS Enclave is operational
    Run 'systeminfo' and look for 'Virtualization Based Security' listed as 'Running' in the output, or check registry key HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard for EnableVirtualizationBasedSecurity set to 1
    Affected if Virtualization-Based Security is not running or not enabled - the vulnerability only applies when VBS Enclave is actually functional on the system
  3. Verify VBS Enclave feature is present
    Run 'Get-VBSEnclave' from PowerShell (requires admin) or check for VBS Enclave-related modules via 'Get-WindowsOptionalFeature -Online' searching for VBS Enclave components
    Affected if The VBS Enclave feature is not installed or not available on the system - exploitation requires this specific enclave feature to be present

A system is affected if it runs a Windows 11 version within the affected build ranges AND has VBS Enclave enabled and operational, allowing a local attacker to potentially elevate privileges within the enclave environment.

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.22621.6060 / 10.0.26100.6899 / 10.0.26200.6899 or later
Fixed in 10.0.22621.606010.0.26100.689910.0.26200.6899
Interim mitigation

Apply the relevant Microsoft Windows security update when available. Verify VBS Enclave functionality remains operational after patching.

Recommended fix High confidence

Windows 11 22h2 build 10.0.22621.6060 or later | Windows 11 23h2 build 10.0.22631.6060 or later | Windows 11 24h2 build 10.0.26100.6899 or later | Windows 11 25h2 build 10.0.26200.6899 or later

  1. Check current Windows version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. Open Settings > Windows Update > Check for updates
  3. Install all available cumulative updates for your Windows 11 version
  4. Restart the system after updates complete
  5. Verify the build version meets or exceeds the fixed threshold: 10.0.22621.6060 for 22h2, 10.0.22631.6060 for 23h2, 10.0.26100.6899 for 24h2, or 10.0.26200.6899 for 25h2
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for critical systems

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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