dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24063

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 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
Heap-based buffer overflow 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

A heap-based buffer overflow vulnerability exists in the Windows Kernel that allows an authenticated local attacker to elevate their privileges to higher permission levels on the affected system.

MitigationApply the Microsoft security update for CVE-2025-24063 to all affected Windows systems; restrict local access to trusted users as an interim compensating control.

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.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061

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. Determine Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from an elevated command prompt to obtain the full version and build number
    Affected if The displayed build number falls below the threshold for your Windows release (e.g., below 10.0.19045.5854 for Windows 10 22h2)
  2. Confirm Windows 10 release
    Run 'winver' to identify the specific Windows 10 release (1507, 1607, 1809, 21h2, or 22h2) and note the displayed build version
    Affected if The build number is less than 21014 for 1507, 8066 for 1607, 7314 for 1809, 5854 for 21h2, or 5854 for 22h2
  3. Confirm Windows 11 release
    Run 'winver' to identify the Windows 11 release (22h2, 23h2, or 24h2) and note the build version shown
    Affected if The build number is less than 22621.5335 for 22h2, 22631.5335 for 23h2, or 26100.4061 for 24h2
  4. Check kernel version via registry
    Query 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' using 'reg query' and note the CurrentBuild and UBR values
    Affected if The CurrentBuild and UBR combined version is lower than the patched build for your Windows release

You are affected if your Windows version build number is below the threshold for your specific Windows release as listed in the affected versions.

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.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the Microsoft security update for CVE-2025-24063 to all affected Windows systems; restrict local access to trusted users as an interim compensating control.

Recommended fix High confidence

Upgrade to the minimum fixed build for your Windows version: 10.0.10240.21014 (Win10 1507), 10.0.14393.8066 (Win10 1607), 10.0.17763.7314 (Win10 1809), 10.0.19044.5854 (Win10 21h2), 10.0.19045.5854 (Win10 22h2), 10.0.22621.5335 (Win11 22h2), 10.0.22631.5335 (Win11 23h2), or 10.0.26100.4061 (Win11 24

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Navigate to Windows Update Settings > Check for updates, or manually download the appropriate update from the Microsoft Update Catalog (catalog.update.microsoft.com)
  3. For Windows 10 1507: Install KB5055523 or later to reach build 10.0.10240.21014
  4. For Windows 10 1607: Install KB5055524 or later to reach build 10.0.14393.8066
  5. For Windows 10 1809: Install KB5055525 or later to reach build 10.0.17763.7314
  6. For Windows 10 21h2: Install KB5055519 or later to reach build 10.0.19044.5854
  7. For Windows 10 22h2: Install KB5055518 or later to reach build 10.0.19045.5854
  8. For Windows 11 22h2: Install KB5055527 or later to reach build 10.0.22621.5335
Caveat Standard Windows update with no expected breaking changes; as a local privilege escalation fix, this is a critical security update that should be applied promptly

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

Fix this in Windows 10 1507 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-24063 — 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-24063 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