dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Dec 2025.
Windows 10 1809Operating system · Microsoft

CVE-2025-62215

HIGH · 7.0 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.17763.8027 / 10.0.19044.6575 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild 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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel 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 race condition vulnerability in the Windows Kernel where improper synchronization of shared resources allows a local authorized attacker to exploit timing-dependent concurrent execution and elevate privileges to a higher permission level.

MitigationApply the latest Microsoft Windows security updates addressing this vulnerability; prioritize patching affected systems and verify successful deployment.

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 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2019Operating system
Affected:< 10.0.17763.8027
Windows Server 2022Operating system
Affected:< 10.0.20348.4346

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. Retrieve Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the installed OS build number
    Affected if The build number is lower than the fixed version for your Windows release (e.g., below 10.0.17763.8027 for Windows 10 1809/Server 2019)
  2. Identify exact Windows release version
    Run 'winver' to see the specific Windows release (such as 1809, 21h2, 22h2, 23h2, 24h2, 25h2) and confirm which affected version range applies
    Affected if The system runs an affected release (Windows 10 1809/21h2/22h2, Windows 11 23h2/24h2/25h2, Server 2019, or Server 2022) with a build below the fixed threshold
  3. Verify security update installation
    Check for KB5048707 or newer security updates by running 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell
    Affected if The security update for CVE-2025-62215 (KB5048707 or subsequent) is not installed on the system
  4. Confirm kernel patch level via registry
    Query the registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' and check the 'CurrentBuild' and 'DisplayVersion' values against unpatched values
    Affected if The CurrentBuild number is below the fixed build number for the respective Windows release

A system is affected if it runs any of the listed Windows versions with a build number below the specified threshold and lacks the CVE-2025-62215 security update.

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.17763.8027 / 10.0.19044.6575 / 10.0.19045.6575 or later
Fixed in 10.0.17763.802710.0.19044.657510.0.19045.6575
Interim mitigation

Apply the latest Microsoft Windows security updates addressing this vulnerability; prioritize patching affected systems and verify successful deployment.

Recommended fix High confidence

Windows 10: upgrade to May 2025 cumulative update (builds 17763.8027, 19044.6575, or 19045.6575 depending on version) | Windows 11: upgrade to May 2025 cumulative update (builds 22631.6199, 26100.7092, or 26200.7092 depending on version) | Windows Server: upgrade to May 2025 cumulative update (build

  1. 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. For Windows 10 1809 (build 17763): Upgrade to build 17763.8027 or later
  3. 3. For Windows 10 21H2 (build 19044): Upgrade to build 19044.6575 or later
  4. 4. For Windows 10 22H2 (build 19045): Upgrade to build 19045.6575 or later
  5. 5. For Windows 11 23H2 (build 22631): Upgrade to build 22631.6199 or later
  6. 6. For Windows 11 24H2 (build 26100): Upgrade to build 26100.7092 or later
  7. 7. For Windows 11 25H2 (build 26200): Upgrade to build 26200.7092 or later
  8. 8. For Windows Server 2019: Upgrade to build 17763.8027 or later
Caveat Standard Windows cumulative update considerations - verify application compatibility before deploying in production environments

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

Fix this in Windows 10 1809 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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