dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53134

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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Ancillary Function Driver for WinSock 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

This is a race condition vulnerability in the Windows Ancillary Function Driver for WinSock (AFD.sys). The flaw involves improper synchronization when handling shared resources, allowing an authenticated local attacker to exploit the race condition and elevate privileges to SYSTEM level.

MitigationApply the Microsoft security update addressing CVE-2025-53134 once released. Monitor Microsoft Security Response Center for patch availability and deploy through standard Windows update channels.

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 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to view the installed Windows build number
    Affected if The build number falls below the first affected version in the range for your Windows release (e.g., < 10.0.10240.21100 for 1507, < 10.0.14393.8330 for 1607, etc.)
  2. Verify AFD.sys driver exists
    Check that C:\Windows\System32\drivers\afd.sys exists on the system
    Affected if The file is present (this is required for the vulnerability to apply; all Windows versions with WinSock have this driver)
  3. Retrieve AFD.sys file version
    Right-click afd.sys in File Explorer, go to Properties > Details, or run 'powershell (Get-Item C:\Windows\System32\drivers\afd.sys).VersionInfo'
    Affected if The file version is below the corresponding patch version for your Windows release (note: Microsoft may not always increment the file version with security updates, so this is supplementary to build checking)

Your system is affected if you are running any Windows 10 or 11 version with a build number lower than the specified threshold for your release channel, and the AFD.sys driver is present on the system.

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 Microsoft security update addressing CVE-2025-53134 once released. Monitor Microsoft Security Response Center for patch availability and deploy through standard Windows update channels.

Recommended fix High confidence

Windows Security Update addressing CVE-2025-53134 (refer to MSRC) - target builds: 10.0.10240.21100 (Win10 1507), 10.0.14393.8330 (Win10 1607), 10.0.17763.7678 (Win10 1809), 10.0.19044.6216 (Win10 21h2), 10.0.19045.6216 (Win10 22h2), 10.0.22621.5768 (Win11 22h2), 10.0.22631.5768 (Win11 23h2), 10.0.2

  1. 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows version (10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, 24h2) is running
  3. 3. Apply the corresponding Windows Security Update from Microsoft Update Catalog or Windows Update that addresses CVE-2025-53134
  4. 4. For Windows 10 1507: update to build 10.0.10240.21100 or later
  5. 5. For Windows 10 1607: update to build 10.0.14393.8330 or later
  6. 6. For Windows 10 1809: update to build 10.0.17763.7678 or later
  7. 7. For Windows 10 21h2: update to build 10.0.19044.6216 or later
  8. 8. For Windows 10 22h2: update to build 10.0.19045.6216 or later
Caveat Standard Windows security update - no expected breaking changes for this privilege escalation patch

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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