dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-58714

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 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
Improper access control 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

Improper access control in Windows Ancillary Function Driver for WinSock (AFD.sys) allows a local authenticated attacker to escalate privileges to SYSTEM level. The AFD driver handles Winsock communications in kernel mode, and the access control flaw enables a low-privileged user to gain elevated access.

MitigationApply Microsoft security updates for CVE-2025-58714 via Windows Update or enterprise patch management systems. Until the patch is available, monitor for suspicious local privilege escalation 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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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 installed Windows 10 version
    Run 'winver' from command prompt or check System Properties. Look for the Build number (e.g., 19045).
    Affected if For Windows 10 1507 (Build 10240): version below 10.0.10240.21161. For Windows 10 1607 (Build 14393): version below 10.0.14393.8519. For Windows 10 1809 (Build 17763): version below 10.0.17763.7919. For Windows 10 21h2 (Build 19044): version below 10.0.19044.6456. For Windows 10 22h2 (Build 19045):
  2. Check installed Windows 11 version
    Run 'winver' from command prompt or check System Properties. Look for the Build number (e.g., 22621).
    Affected if For Windows 11 22h2 (Build 22621): version below 10.0.22621.6060. For Windows 11 23h2 (Build 22631): version 10.0.22631.6060 or below. For Windows 11 24h2 (Build 26100): version below 10.0.26100.6899.
  3. Verify exact build number via command line
    Open Command Prompt or PowerShell and run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or 'winver /B' to get precise build information including the full version string.
    Affected if The full version string (such as 10.0.19045.1234) is lower than the fixed version for your specific Windows release.

You are affected if your Windows version build number falls below the fixed build number for your specific Windows release (10/11) and edition (1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2).

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply Microsoft security updates for CVE-2025-58714 via Windows Update or enterprise patch management systems. Until the patch is available, monitor for suspicious local privilege escalation attempts.

Recommended fix High confidence

Install Windows security updates from Microsoft Update (monthly cumulative updates containing the fix for CVE-2025-58714)

  1. Open Windows Update by pressing Windows key + I, then navigate to Update & Security > Windows Update
  2. Click 'Check for updates' and install all available security updates
  3. Alternatively, manually download and install the specific security update from Microsoft Update Catalog for your Windows version
  4. After installation, restart the computer to apply the changes
  5. Verify the build version matches or exceeds the fixed version for your Windows release (e.g., Windows 11 22h2 should be >= 10.0.22621.6060)

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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