dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53140

HIGH · 7.0 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 →
72/100
Remediation priority · Elevated
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 Kernel Transaction Manager 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 Transaction Manager allows a local, authorized attacker to escalate privileges to higher integrity levels by exploiting a dangling pointer after memory deallocation.

MitigationApply the relevant Microsoft security patch for this vulnerability once released. Until then, restrict local administrative access and monitor for suspicious kernel-mode activity.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 major version
    Run 'winver' from command prompt or check the 'OS Name' field in the output of 'systeminfo' command
    Affected if The system runs any Windows 10 or Windows 11 edition (the vulnerability affects both)
  2. Obtain exact Windows build number
    Run 'systeminfo' and note the 'OS Version' entry (format: 10.0.XXXXX.XXXXX) or run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber'
    Affected if The build number is lower than the thresholds for your Windows release (see version ranges)
  3. Identify Windows 10 release
    Run 'winver' or check 'systeminfo' to determine if the system is version 1507, 1607, 1809, 21h2, or 22h2
    Affected if Version is 1507 and build < 10240.21100, OR 1607 and build < 14393.8330, OR 1809 and build < 17763.7678, OR 21h2 and build < 19044.6216, OR 22h2 and build < 19045.6216
  4. Identify Windows 11 release
    Run 'winver' or check 'systeminfo' to determine if the system is version 22h2, 23h2, or 24h2
    Affected if Version is 22h2 and build < 22621.5768, OR 23h2 and build < 22631.5768, OR 24h2 and build < 26100.4851

If your installed Windows build number falls below any of the version-specific thresholds listed for your Windows release, the system is vulnerable to this privilege escalation flaw in the Kernel Transaction Manager.

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 the relevant Microsoft security patch for this vulnerability once released. Until then, restrict local administrative access and monitor for suspicious kernel-mode activity.

Recommended fix High confidence

Install the appropriate Windows cumulative security update containing KB5055525 (or subsequent updates) for your Windows version reaching: 10.0.10240.21100 (1507), 10.0.14393.8330 (1607), 10.0.17763.7678 (1809), 10.0.19044.6216 (21h2), 10.0.19045.6216 (22h2), 10.0.22621.5768 (11 22h2), 10.0.22631.57

  1. Identify your current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which version range your current build falls into from the affected versions list
  3. Apply the latest Windows Security Update or Cumulative Update for your specific Windows version that includes the fix for CVE-2025-53140
  4. Restart the system after applying the update
  5. Verify the update was successfully installed by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version for your release
Caveat Standard Windows update - no expected breaking changes for this security patch; however, test in staging if possible

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
84.0 hours of engineering $14,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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