dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27735

MEDIUM · 6.0 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
62/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
Insufficient verification of data authenticity in Windows Virtualization-Based Security (VBS) Enclave allows an authorized attacker to bypass a security feature 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 vulnerability in Windows Virtualization-Based Security (VBS) Enclave involves insufficient verification of data authenticity, allowing a locally authorized attacker to bypass a security feature. VBS is a Windows security feature that creates isolated enclaves using hardware virtualization, and the flaw permits an attacker with local access to circumvent protections meant to ensure data integrity.

MitigationApply the relevant Windows security update once released by Microsoft to address the VBS Enclave authentication bypass. Organizations using VBS enclaves should verify their current patch levels and monitor for applicable security bulletins.

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.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

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
None

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

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. Verify VBS is enabled on the system
    Run `systeminfo` from an elevated command prompt and look for the 'Virtualization-Based Security' line, or run `msinfo32` and check the 'Virtualization-Based Security' field under Device Security Information. Alternatively, check registry key `HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\EnableVirtualizationBasedSecurity` (value should be 1).
    Affected if VBS is not running (value is disabled or not present) - the vulnerability only applies when VBS is active.
  2. Confirm Windows 10 version and build number
    Run `winver` or `systeminfo` to obtain the exact OS build number. For Windows 10, identify the release (1507, 1607, 1809, 21h2, or 22h2) from the version displayed and note the full build number shown (for example, 10.0.19045.xxxx).
    Affected if The build number is lower than 10.0.10240.20978 (1507), 10.0.14393.7969 (1607), 10.0.17763.7136 (1809), 10.0.19044.5737 (21h2), or 10.0.19045.5737 (22h2).
  3. Confirm Windows 11 version and build number
    Run `winver` or `systeminfo` to obtain the exact OS build number. For Windows 11, identify the release (22h2, 23h2, or 24h2) from the version displayed and note the full build number shown (for example, 10.0.22621.xxxx).
    Affected if The build number is lower than 10.0.22621.5189 (22h2), 10.0.22631.5189 (23h2), or 10.0.26100.3775 (24h2).
  4. Verify VBS Enclave feature status
    Check if VBS Enclave functionality is in use by examining running services or processes that rely on hardware virtualization enclaves. This can be confirmed via the 'Device Security' page in Windows Security app, which shows whether 'Memory Integrity' or 'Kernel Code Integrity' protections are active - these utilize VBS.
    Affected if VBS Enclave features are actively being used (Memory Integrity or Kernel Code Integrity enabled) on an affected Windows version.

The system is affected if VBS is enabled and the Windows build number falls below the threshold for the corresponding version, as listed in the affected version ranges.

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.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply the relevant Windows security update once released by Microsoft to address the VBS Enclave authentication bypass. Organizations using VBS enclaves should verify their current patch levels and monitor for applicable security bulletins.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20978 | Windows 10 1607: 10.0.14393.7969 | Windows 10 1809: 10.0.17763.7136 | Windows 10 21h2: 10.0.19044.5737 | Windows 10 22h2: 10.0.19045.5737 | Windows 11 22h2: 10.0.22621.5189 | Windows 11 23h2: 10.0.22631.5189 | Windows 11 24h2: 10.0.26100.3775

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click Check for updates to download and install the latest security updates
  3. Alternatively, manually install the appropriate security update from the Microsoft Update Catalog for your specific Windows version and build
  4. Restart the system after the update is installed to apply the changes
  5. Verify the installed build version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update - minimal risk of breaking changes; as with any system update, ensure backups and test in non-production environments first

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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