dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-53151

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.17763.7678 / 10.0.19044.6216 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 authenticated attacker to elevate privileges. The flaw occurs when the kernel frees memory but a pointer to that memory location is still retained, potentially allowing the attacker to manipulate the freed memory and gain elevated system privileges.

MitigationApply the relevant Microsoft security update for this vulnerability to all affected Windows systems. Prioritize patching systems with direct user access as the attack requires local 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 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
Windows Server 2019Operating system
Affected:< 10.0.17763.7678
Windows Server 2022Operating system
Affected:< 10.0.20348.3989

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 Windows build version
    Run 'systeminfo' from command prompt or check 'winver' output. Note the OS Name and OS Version/Build Number fields.
    Affected if The build number (e.g., 10.0.17763.xxxx) is lower than the fixed version for your Windows edition.
  2. Confirm Windows edition
    Review the OS Name from systeminfo output to determine if you are running Windows 10 (1809, 21h2, 22h2), Windows 11 (22h2, 23h2, 24h2), Windows Server 2019, or Windows Server 2022.
    Affected if Your edition matches one of the affected product lines listed in the CVE.
  3. Compare build against fixed versions
    For your identified edition, compare your installed build number: Windows 10 1809/Server 2019 must be >= 10.0.17763.7678; Windows 10 21h2 >= 10.0.19044.6216; Windows 10 22h2 >= 10.0.19045.6216; Windows 11 22h2 >= 10.0.22621.5768; Windows 11 23h2 >= 10.0.22631.5768; Windows 11 24h2 >= 10.0.26100.4851; Windows Server 2022 >= 10.0.20348.3989.
    Affected if Your current build number is less than the required fixed build for your specific Windows edition.

You are affected if your Windows version and build number fall within the affected ranges and have not received 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.17763.7678 / 10.0.19044.6216 / 10.0.19045.6216 or later
Fixed in 10.0.17763.767810.0.19044.621610.0.19045.6216
Interim mitigation

Apply the relevant Microsoft security update for this vulnerability to all affected Windows systems. Prioritize patching systems with direct user access as the attack requires local access.

Recommended fix High confidence

Install the January 2025 Windows security update (KB5055527 or corresponding KB for your version) which contains the fix for CVE-2025-53151

  1. 1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. 2. Determine which update applies to your system by checking the Windows version (1809, 21h2, 22h2, 23h2, 24h2, Server 2019, or Server 2022)
  3. 3. Apply the relevant security update from Microsoft Update Catalog or Windows Update. For this CVE (January 2025 Patch Tuesday), obtain the KB number from the Microsoft Security Response Center (msrc.microsoft.com) for your specific Windows version
  4. 4. Restart the system after applying the update
  5. 5. Verify the installed build matches or exceeds the fixed version: 10.0.17763.7678 (Windows 10 1809/Server 2019), 10.0.19044.6216 (Windows 10 21h2), 10.0.19045.6216 (Windows 10 22h2), 10.0.22621.5768 (Windows 11 22h2), 10.0.22631.5768 (Windows 11 23h2), 10.0.26100.4851 (Windows 11 24h2), or 10.0.20348.3989 (Windows Server 2022)
Caveat Standard Windows monthly update with no known breaking changes; as a kernel privilege elevation fix, it may require a reboot

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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