CyberSecBulletin
CVE-2026-35424NVD status: Analyzed

Windows 10 Version 1607: Missing Release of Memory after Effective Lifetime

Published Updated By the CyberSecBulletin desk

CVE-2026-35424 is a high-severity missing release of memory after effective lifetime vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 10.0.14393.9140 as the first without the flaw, so updating Windows 10 Version 1607 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.19% chance of exploitation within 30 days, higher than 68% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Windows 10 Version 1607 to 10.0.14393.9140 or a later version.
  2. Update Windows 10 Version 1809 to 10.0.17763.8755 or a later version.
  3. Update Windows 10 Version 21H2 to 10.0.19044.7291 or a later version.
  4. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.914010.0.14393.9140
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.875510.0.17763.8755
MicrosoftWindows 10 Version 21H210.0.19044.0 up to, but not including, 10.0.19044.729110.0.19044.7291
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.741710.0.19045.7417
MicrosoftWindows 11 version 23H210.0.22631.0 up to, but not including, 10.0.22631.7079; 10.0.22631.0 up to, but not including, 10.0.22631.721910.0.22631.7079, 10.0.22631.7219
MicrosoftWindows 11 Version 24H210.0.26100.0 up to, but not including, 10.0.26100.845710.0.26100.8457
MicrosoftWindows 11 Version 25H210.0.26200.0 up to, but not including, 10.0.26200.845710.0.26200.8457
MicrosoftWindows 11 version 26H110.0.28000.0 up to, but not including, 10.0.28000.211310.0.28000.2113
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.260796.2.9200.26079
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.260796.2.9200.26079
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.231816.3.9600.23181
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.231816.3.9600.23181
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.914010.0.14393.9140
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.914010.0.14393.9140
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.875510.0.17763.8755
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.875510.0.17763.8755
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.513910.0.20348.5139
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0 up to, but not including, 10.0.25398.233010.0.25398.2330
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.3286010.0.26100.32860
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.3286010.0.26100.32860
MicrosoftWindows 10 1607before 10.0.14393.914010.0.14393.9140
MicrosoftWindows 10 1809before 10.0.17763.875510.0.17763.8755
MicrosoftWindows 10 21h2before 10.0.19044.729110.0.19044.7291
MicrosoftWindows 10 22h2before 10.0.19045.729110.0.19045.7291
MicrosoftWindows 11 23h2before 10.0.22631.707910.0.22631.7079

Version data comes from the organisation that assigned the CVE; 4 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (microsoft.com).

Official description

Missing release of memory after effective lifetime in Windows Internet Key Exchange (IKE) Protocol allows an unauthorized attacker to deny service over a network.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Release of Memory after Effective Lifetime

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How developers prevent this class of flaw

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC). To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.

More Missing Release of Memory after Effective Lifetime vulnerabilities (CWE-401)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Missing Release of Memory after Effective Lifetime vulnerabilities

Spotted an error? Tell us.