dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49686

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 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 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 null pointer dereference vulnerability exists in the Windows TCP/IP stack that can be exploited locally by an authorized attacker to achieve privilege escalation, potentially gaining elevated system privileges.

MitigationApply the relevant Microsoft security update for CVE-2025-49686 to all affected Windows systems. Prioritize systems that allow local access to untrusted users.

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.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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 number
    Run 'winver' from command prompt or check the Build number in System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The displayed build number falls below any of these thresholds: 10240.21073 (Win10 1507), 14393.8246 (Win10 1607), 17763.7558 (Win10 1809), 19044.6093 (Win10 21h2), 19045.6093 (Win10 22h2), 22621.5624 (Win11 22h2), 22631.5624 (Win11 23h2), or 26100.4652 (Win11 24h2)
  2. Verify TCP/IP stack is present
    Confirm TCP/IP protocol is enabled by checking network adapter properties or running 'netsh int ip show config'
    Affected if TCP/IP is installed and the Windows version is below the safe build thresholds listed above (vulnerability is in the Windows TCP/IP stack itself)
  3. Confirm local attacker scenario
    Review system permissions to determine if untrusted local users have access to interactive logon
    Affected if The system has local user accounts with limited privileges and the Windows build is below the safe thresholds - such accounts could potentially exploit this flaw for privilege escalation

The system is affected if it runs any Windows version with a build number lower than the safe thresholds for its respective release, and it allows local untrusted user access.

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.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the relevant Microsoft security update for CVE-2025-49686 to all affected Windows systems. Prioritize systems that allow local access to untrusted users.

Recommended fix High confidence

Install the appropriate Windows security update containing the fix for CVE-2025-49686. For Windows 10 1507 upgrade to build 10.0.10240.21073 or later; Windows 10 1607 to 10.0.14393.8246 or later; Windows 10 1809 to 10.0.17763.7558 or later; Windows 10 21h2 to 10.0.19044.6093 or later; Windows 10 22h

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or 11 version and build you are running from the affected versions list
  3. 3. Open Settings > Windows Update and check for available security updates
  4. 4. Alternatively, manually check for updates using Windows Update or download specific updates from Microsoft Update Catalog
  5. 5. Apply the latest cumulative security update for your specific Windows version
  6. 6. After installation, restart the system to complete the patch
  7. 7. Verify the installation was successful by checking that the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update; no breaking changes expected for this security patch, though testing in non-production environments is recommended

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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