dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24066

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.10240.20947 / 10.0.14393.7876 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-Mode Drivers 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

Heap-based buffer overflow in Windows kernel-mode drivers allows a local authorized attacker to exploit memory corruption and elevate privileges to higher integrity levels.

MitigationApply Microsoft security updates for affected Windows versions; prioritize patching endpoints and servers where untrusted local users could gain elevated access.

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.20947
Windows 10 1607Operating system
Affected:< 10.0.14393.7876
Windows 10 21h2Operating system
Affected:< 10.0.19044.5608
Windows 10 22h2Operating system
Affected:< 10.0.19045.5608
Windows 11 22h2Operating system
Affected:< 10.0.22621.5039
Windows 11 23h2Operating system
Affected:< 10.0.22631.5039
Windows 11 24h2Operating system
Affected:< 10.0.26100.3403> 10.0.26100.3403, < 10.0.26100.3476
Windows Server 2016Operating system
Affected:< 10.0.14393.7876

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. Check Windows 10 version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the full version and build number
    Affected if The version is 10.0.10240.x with x < 20947, OR 10.0.14393.x with x < 7876, OR 10.0.19044.x with x < 5608, OR 10.0.19045.x with x < 5608
  2. Check Windows 11 version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the full version and build number
    Affected if The version is 10.0.22621.x with x < 5039, OR 10.0.22631.x with x < 5039, OR 10.0.26100.3403 or lower, OR between 10.0.26100.3404 and 10.0.26100.3475 inclusive
  3. Check Windows Server 2016 version
    Run 'winver' or 'systeminfo' to retrieve the Windows Server 2016 build number
    Affected if The version shows 10.0.14393.x with x < 7876
  4. Verify installed security updates
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security updates
    Affected if No security update matching this CVE (typically labeled KB5000XXX) appears in the installed updates list for systems with versions in the affected ranges

The system is affected if it runs any of the listed Windows versions below the specified build thresholds and is missing the corresponding 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.10240.20947 / 10.0.14393.7876 / 10.0.19044.5608 or later
Fixed in 10.0.10240.2094710.0.14393.787610.0.19044.5608
Interim mitigation

Apply Microsoft security updates for affected Windows versions; prioritize patching endpoints and servers where untrusted local users could gain elevated access.

Recommended fix High confidence

Windows 10 1507: build 10.0.10240.20947 or later | Windows 10 1607/Server 2016: build 10.0.14393.7876 or later | Windows 10 21h2: build 10.0.19044.5608 or later | Windows 10 22h2: build 10.0.19045.5608 or later | Windows 11 22h2: build 10.0.22621.5039 or later | Windows 11 23h2: build 10.0.22631.503

  1. Identify the current Windows build version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. Determine which version branch your current build belongs to (1507, 1607, 21h2, 22h2, 24h2, or Server 2016)
  3. Navigate to Windows Settings > Update & Security > Windows Update and check for updates
  4. Alternatively, manually download the appropriate cumulative update from the Microsoft Update Catalog for your specific Windows version and build
  5. Install the security update that includes the fix for CVE-2025-24066
  6. Restart the system when prompted to complete the installation
  7. Verify the update was installed successfully by checking the installed updates via `Get-HotFix` or reviewing the Windows Update history
Caveat Standard Windows update - no breaking changes expected for this security patch; standard enterprise rollback procedures apply if issues arise

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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