Network denial of service via unreleased memory
Published Sep 8, 2026 · Updated Sep 9, 2026
Memory-release failure in Windows TCP/IP allows remote attackers to interrupt affected Windows systems through network traffic. The TCP/IP implementation retains allocated memory after its effective lifetime instead of releasing it; Microsoft has not identified the packet type or code path. No authentication or user interaction is required, and published material does not specify whether the endpoint hangs, crashes, or recovers.
Summary
What happened
Memory-release failure in Windows TCP/IP allows remote attackers to interrupt affected Windows systems through network traffic. The TCP/IP implementation retains allocated memory after its effective lifetime instead of releasing it; Microsoft has not identified the packet type or code path. No authentication or user interaction is required, and published material does not specify whether the endpoint hangs, crashes, or recovers.
The record
- CVE
- CVE-2026-69588
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2025 (Server Core installation)
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.26100.0 <10.0.26100.33438
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo