dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53141

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
Null pointer dereference 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

A null pointer dereference vulnerability exists in the Windows Ancillary Function Driver for WinSock (AFD.sys). An authorized local attacker can exploit this memory corruption issue to elevate their privileges from a standard user account to SYSTEM-level access.

MitigationApply the Microsoft security update for CVE-2025-53141 once released. This is a Windows kernel-level vulnerability requiring an OS patch rather than application-level remediation.

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. Check Windows build version
    Open Command Prompt and run `winver` or `systeminfo | findstr /B /C:"OS Version"` to retrieve the installed Windows build number
    Affected if The build number is lower than any of the following thresholds: 10240.21100 (1507), 14393.8330 (1607), 17763.7678 (1809), 19044.6216 (21h2), 19045.6216 (22h2), 22621.5768 (22h2), 22631.5768 (23h2), 26100.4851 (24h2)
  2. Identify Windows release branch
    Run `systeminfo` and note the "OS Configuration" and "Build" fields to determine which Windows 10 or 11 release (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2) is installed
    Affected if The detected release matches an affected version range and the build number falls below the corresponding fixed threshold listed in the CVE
  3. Verify AFD.sys version
    Navigate to C:\Windows\System32\drivers\AFD.sys, right-click the file, select Properties, and check the File Version field under the Details tab
    Affected if The AFD.sys file version is lower than the version bundled with the fixed Windows builds (the build numbers above), indicating the vulnerability remains unpatched

The system is affected if the installed Windows build number is below the fixed threshold for its specific release version, as listed in the CVE-affected products and 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 the Microsoft security update for CVE-2025-53141 once released. This is a Windows kernel-level vulnerability requiring an OS patch rather than application-level remediation.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21100 | Windows 10 1607: 10.0.14393.8330 | Windows 10 1809: 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

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Ensure the update includes the patch for CVE-2025-53141 (check release notes for build numbers)
  4. Restart the system when prompted to complete the installation
  5. Verify the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update; test in staging environment for enterprise deployments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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