dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-26686

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Sensitive data storage in improperly locked memory in Windows TCP/IP allows an unauthorized attacker to execute code over a network.

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 vulnerability in Windows TCP/IP stack involves sensitive data being stored in memory that is not properly locked (non-pageable). Improperly locked memory can potentially be paged to disk or accessed in ways that bypass expected memory protection, allowing a remote unauthenticated attacker to execute code over a network by exploiting the insecure memory handling.

MitigationApply Microsoft security updates for Windows when available. In interim, network segmentation and firewall rules may limit attack surface. Review memory allocation patterns in custom network applications.

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.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Identify Windows version and build number
    Run 'winver' from the command prompt or check 'System Information' (msinfo32) to find the Windows edition, version, and build number (e.g., 10.0.19045.5737)
    Affected if The build number displayed is lower than the threshold for your specific Windows release (see version-specific thresholds in other steps)
  2. Determine Windows 10 release version
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify if you are on Windows 10 and which release (1507, 1607, 1809, 21h2, or 22h2)
    Affected if Running Windows 10 with build below 10.0.10240.20978 (1507), 10.0.14393.7969 (1607), 10.0.17763.7136 (1809), 10.0.19044.5737 (21h2), or 10.0.19045.5737 (22h2)
  3. Determine Windows 11 version
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify if you are on Windows 11 and the release (22h2, 23h2, or 24h2)
    Affected if Running Windows 11 with build below 10.0.22621.5189 (22h2), 10.0.22631.5189 (23h2), or 10.0.26100.3775 (24h2)
  4. Verify TCP/IP stack is in use
    Confirm TCP/IP is enabled by checking network adapter status via 'netsh interface ipv4 show interfaces' or viewing active network connections
    Affected if TCP/IP networking is enabled (the vulnerability exists in the Windows TCP/IP stack, so any system using TCP/IP networking is potentially affected if version is vulnerable)
  5. Confirm non-pageable memory handling context
    This is an internal Windows memory allocation issue in the TCP/IP stack. No direct configuration check is possible from userland. The vulnerability is present if the Windows version is in the affected build range.
    Affected if System is running a Windows version with build number below the thresholds listed in steps 2-3 AND TCP/IP networking is active

A system is affected if it runs any Windows 10 or Windows 11 version with a build number lower than the patched thresholds AND has TCP/IP networking enabled, as the vulnerability resides in the Windows TCP/IP stack memory handling.

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.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply Microsoft security updates for Windows when available. In interim, network segmentation and firewall rules may limit attack surface. Review memory allocation patterns in custom network applications.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20978 | Windows 10 1607: 10.0.14393.7969 | Windows 10 1809: 10.0.17763.7136 | Windows 10 21h2: 10.0.19044.5737 | Windows 10 22h2: 10.0.19045.5737 | Windows 11 22h2: 10.0.22621.5189 | Windows 11 23h2: 10.0.22631.5189 | Windows 11 24h2: 10.0.26100.3775

  1. Open Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Restart the computer when prompted to complete the installation
  4. Verify the update was installed by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update - minimal risk; patch at earliest convenience given remote code execution severity

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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