dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54093

HIGH · 7.0 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.10240.21128 / 10.0.14393.8422 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
Time-of-check time-of-use (toctou) race condition in Windows TCP/IP 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 time-of-check time-of-use (TOCTOU) race condition exists in the Windows TCP/IP stack that allows a locally authorized attacker to manipulate the timing between a security check and the use of that check's result, enabling local privilege elevation from a lower-privileged context to higher system privileges.

MitigationApply Microsoft security patches for this vulnerability immediately. Until patched, limit local user privileges to the minimum required and monitor for suspicious process activity that could indicate exploitation attempts.

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.21128
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
Windows 10 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508

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 build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the installed build
    Affected if The build number is lower than the fixed version for your Windows release (10.0.10240.21128 for 1507, 10.0.14393.8422 for 1607, 10.0.17763.7792 for 1809, 10.0.19044.6332 or 10.0.19045.6332 for 10, 10.0.22621.5909 for 11 22h2, 10.0.22631.5909 for 11 23h2, 10.0.26100.6508 for 11 24h2)
  2. Identify Windows release version
    Run 'winver' to confirm whether you are on Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 22h2, 23h2, 24h2
    Affected if The release corresponds to an affected version branch with a build number below the fixed threshold
  3. Confirm TCP/IP stack is present
    Verify the Windows networking stack is operational by checking that network adapters are available via 'ipconfig /all' or 'Get-NetAdapter' in PowerShell
    Affected if The TCP/IP stack is present on any Windows system, which is the default configuration; the vulnerability exists in the TCP/IP stack itself regardless of configuration

The system is affected if the installed Windows build number falls below the fixed build for your specific Windows release version.

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.21128 / 10.0.14393.8422 / 10.0.17763.7792 or later
Fixed in 10.0.10240.2112810.0.14393.842210.0.17763.7792
Interim mitigation

Apply Microsoft security patches for this vulnerability immediately. Until patched, limit local user privileges to the minimum required and monitor for suspicious process activity that could indicate exploitation attempts.

Recommended fix High confidence

Windows 10 1507 to 10.0.10240.21128+ | Windows 10 1607 to 10.0.14393.8422+ | Windows 10 1809 to 10.0.17763.7792+ | Windows 10 21h2 to 10.0.19044.6332+ | Windows 10 22h2 to 10.0.19045.6332+ | Windows 11 22h2 to 10.0.22621.5909+ | Windows 11 23h2 to 10.0.22631.5909+ | Windows 11 24h2 to 10.0.26100.650

  1. 1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or 11 version and build is currently installed from the list: 1507, 1607, 1809, 21h2, 22h2, 22h2 (Windows 11), 23h2 (Windows 11), or 24h2 (Windows 11)
  3. 3. Check if the current build number is below the fixed version for your release: 10.0.10240.21128 (1507), 10.0.14393.8422 (1607), 10.0.17763.7792 (1809), 10.0.19044.6332 (21h2), 10.0.19045.6332 (22h2), 10.0.22621.5909 (Win11 22h2), 10.0.22631.5909 (Win11 23h2), or 10.0.26100.6508 (Win11 24h2)
  4. 4. If vulnerable, apply the latest Windows Updates by navigating to Settings > Update & Security > Windows Update and selecting 'Check for updates'
  5. 5. Alternatively, manually download and install the specific cumulative update from the Microsoft Update Catalog matching your Windows version
  6. 6. After installation, restart the system to apply the TCP/IP security update
  7. 7. Verify the fix by checking the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks: update may require restart, ensure backups and 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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