dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-64658

HIGH · 7.5 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.17763.8146 / 10.0.19044.6691 or later.
See remediation →
75/100
Remediation priority · High

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 Shell 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 race condition vulnerability exists in Windows Shell where concurrent execution accesses a shared resource without proper synchronization. An authorized local attacker can exploit this timing vulnerability to elevate privileges from their current user level to higher system privileges.

MitigationApply Microsoft security updates for Windows Shell when released. Prioritize patching systems where users have any level of access. Monitor vendor advisories for patch availability.

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.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2019Operating system
Affected:< 10.0.17763.8146
Windows Server 2022Operating system
Affected:< 10.0.20348.4467

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/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 execute 'systeminfo' and locate the OS Version line to obtain the full build number including the revision (for example: 10.0.17763.8146)
    Affected if The build number is lower than the threshold for your specific Windows version and release
  2. Identify Windows release
    Run 'winver' to determine the Windows release (such as Windows 10 1809, 21h2, 22h2, Windows 11 23h2, 24h2, 25h2, Windows Server 2019, or Windows Server 2022)
    Affected if The system runs any of the affected releases listed in the CVE
  3. Compare against affected version thresholds
    Match your identified release to its corresponding vulnerable build range: Windows 10 1809/Server 2019: <10.0.17763.8146; Windows 10 21h2: <10.0.19044.6691; Windows 10 22h2: <10.0.19045.6691; Windows 11 23h2: <10.0.22631.6345; Windows 11 24h2: <10.0.26100.7392; Windows 11 25h2: <10.0.26200.7392; Windows Server 2022: <10.0.20348.4467
    Affected if Your current build number falls below the threshold for your specific Windows release

The environment is affected if the installed Windows version matches one of the listed releases AND the build number is below the corresponding threshold, since the race condition exists in the Windows Shell component present on all such systems.

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.8146 / 10.0.19044.6691 / 10.0.19045.6691 or later
Fixed in 10.0.17763.814610.0.19044.669110.0.19045.6691
Interim mitigation

Apply Microsoft security updates for Windows Shell when released. Prioritize patching systems where users have any level of access. Monitor vendor advisories for patch availability.

Recommended fix High confidence

Windows Security Update including CVE-2025-64658 patch for your specific Windows version

  1. Open Settings on the Windows machine
  2. Navigate to Windows Update (Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the update includes the patch for CVE-2025-64658 (Windows Shell security update)
  5. Restart the computer when prompted to complete the installation
  6. Verify the installed build version matches or exceeds the fixed version for your Windows edition (e.g., win10 1809: 10.0.17763.8146, win11 23h2: 10.0.22631.6345, Server 2022: 10.0.20348.4467)

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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