dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59207

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.19044.6456 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
Untrusted pointer dereference 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 local privilege escalation vulnerability in the Windows Kernel stemming from an untrusted pointer dereference flaw. An authenticated attacker can exploit this to elevate their privileges from a standard user to higher-level system access by manipulating how the kernel handles pointer references in memory.

MitigationApply the Microsoft security update for CVE-2025-59207 once released through Windows Update or patch management systems. Prioritize endpoints based on exposure to untrusted local users.

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.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
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
Windows Server 2019Operating system
Affected:< 10.0.17763.7919

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. Retrieve Windows version and build number
    Open Command Prompt and run 'winver' or 'ver' to display the Windows version and build number. Alternatively, run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' for detailed information.
    Affected if The displayed build number is lower than the threshold for your Windows edition (17763.7919 for 1809/Server 2019, 19044.6456 for 21h2, 19045.6456 for 22h2, 22621.6060 for 11 22h2, 22631.6060 for 11 23h2, 26100.6899 for 11 24h2, 26200.6899 for 11 25h2).
  2. Confirm Windows edition or Server version
    Check if the system is running Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 22h2/23h2/24h2/25h2, or Windows Server 2019. Use 'winver' or 'systeminfo' to identify the exact edition.
    Affected if The system runs any of the affected editions listed in the CVE (Windows 10 1809/21h2/22h2, Windows 11 22h2/23h2/24h2/25h2, or Windows Server 2019).
  3. Compare build number against CVE thresholds
    Take the build number from step 1 (the numeric value after 10.0) and compare it directly to the fixed version numbers in the CVE. For example, Windows 10 22h2 should be below 19045.6456, Windows 11 23h2 should be below or equal to 22631.6060.
    Affected if The installed build number falls below the specific threshold for that Windows edition as listed in the affected products.

The system is affected if it runs any of the listed Windows 10, Windows 11, or Windows Server 2019 editions with a build number lower than the specified threshold for that edition.

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.7919 / 10.0.19044.6456 / 10.0.19045.6456 or later
Fixed in 10.0.17763.791910.0.19044.645610.0.19045.6456
Interim mitigation

Apply the Microsoft security update for CVE-2025-59207 once released through Windows Update or patch management systems. Prioritize endpoints based on exposure to untrusted local users.

Recommended fix High confidence

Windows 10 1809 (build 10.0.17763.7919+), Windows 10 21h2 (build 10.0.19044.6456+), Windows 10 22h2 (build 10.0.19045.6456+), Windows 11 22h2 (build 10.0.22621.6060+), Windows 11 23h2 (build 10.0.22631.6061+), Windows 11 24h2 (build 10.0.26100.6899+), Windows 11 25h2 (build 10.0.26200.6899+), Window

  1. Identify the current Windows version and build number (winver or systeminfo)
  2. For Windows 10 1809: Upgrade to build 10.0.17763.7919 or later
  3. For Windows 10 21h2: Upgrade to build 10.0.19044.6456 or later
  4. For Windows 10 22h2: Upgrade to build 10.0.19045.6456 or later
  5. For Windows 11 22h2: Upgrade to build 10.0.22621.6060 or later
  6. For Windows 11 23h2: Upgrade to build higher than 10.0.22631.6060
  7. For Windows 11 24h2: Upgrade to build 10.0.26100.6899 or later
  8. For Windows 11 25h2: Upgrade to build 10.0.26200.6899 or later
Caveat Standard Windows update; no expected breaking changes for this security patch

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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