dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49761

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21100 / 10.0.14393.8330 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
Use after free 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 use-after-free vulnerability in the Windows Kernel enables a local authorized attacker to elevate privileges to higher permission levels. This type of memory corruption flaw allows the attacker to manipulate freed memory allocations to execute arbitrary code in kernel mode.

MitigationApply Microsoft security updates for Windows Kernel once available; prioritize patching affected systems according to enterprise change management procedures.

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.21100
Windows 10 1607Operating system
Affected:< 10.0.14393.8330
Windows 10 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851

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. Identify installed Windows version and build number
    Run `winver` to display the Windows version and build, or run `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` for detailed version information
    Affected if The displayed build number falls below any of the thresholds listed in the affected version ranges for your Windows edition (10 1507, 1607, 1809, 21h2, 22h2 or 11 22h2, 23h2, 24h2)
  2. Confirm Windows 10 edition if applicable
    Run `winver` or check System Properties to determine if the system is Windows 10 1507, 1607, 1809, 21h2, or 22h2; compare the build number to the specific threshold for that edition
    Affected if Running an affected Windows 10 edition with a build number lower than its respective threshold (10240.21100, 14393.8330, 17763.7678, 19044.6216, or 19045.6216)
  3. Confirm Windows 11 edition if applicable
    Run `winver` or check System Properties to determine if the system is Windows 11 22h2, 23h2, or 24h2; compare the build number to the specific threshold for that edition
    Affected if Running an affected Windows 11 edition with a build number lower than its respective threshold (22621.5768, 22631.5768, or 26100.4851)

The system is affected if it runs any of the listed Windows 10 or Windows 11 editions with a build number below the corresponding threshold for that edition, as the use-after-free flaw exists in the unpatched kernel of those 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.21100 / 10.0.14393.8330 / 10.0.17763.7678 or later
Fixed in 10.0.10240.2110010.0.14393.833010.0.17763.7678
Interim mitigation

Apply Microsoft security updates for Windows Kernel once available; prioritize patching affected systems according to enterprise change management procedures.

Recommended fix High confidence

Upgrade to the minimum fixed build for your Windows version: Windows 10 1507 to 10.0.10240.21100 | Windows 10 1607 to 10.0.14393.8330 | Windows 10 1809 to 10.0.17763.7678 | Windows 10 21h2 to 10.0.19044.6216 | Windows 10 22h2 to 10.0.19045.6216 | Windows 11 22h2 to 10.0.22621.5768 | Windows 11 23h2

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which affected version range your current build falls into from the CVE advisory
  3. Apply the corresponding security update from Windows Update, Microsoft Update Catalog, or via WSUS/SCCM for enterprise deployments
  4. After installation, restart the system to ensure the kernel patch is fully applied
  5. Verify the installed build matches or exceeds the fixed version (e.g., for Windows 10 22h2, ensure build is 10.0.19045.6216 or higher)
Caveat Standard Windows update with no breaking changes expected; test critical applications in enterprise environments before broad deployment

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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