Unauthenticated service interruption via unreleased memory
Published Sep 8, 2026 · Updated Sep 9, 2026
Memory leak in Microsoft Windows DHCP Server allows remote attackers to interrupt DHCP service by sending network traffic. Microsoft identifies the flaw only as failure to release memory after its effective lifetime and has not disclosed the responsible request handler or allocation path. Exploitation requires no authentication but does require the DHCP Server component to process network traffic, and repeated triggering exhausts memory until service is interrupted.
Summary
What happened
Memory leak in Microsoft Windows DHCP Server allows remote attackers to interrupt DHCP service by sending network traffic. Microsoft identifies the flaw only as failure to release memory after its effective lifetime and has not disclosed the responsible request handler or allocation path. Exploitation requires no authentication but does require the DHCP Server component to process network traffic, and repeated triggering exhausts memory until service is interrupted.
The record
- CVE
- CVE-2026-70065
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-401, T1499
- 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.17763.0 <10.0.17763.9245
What conditions does exploitation require?
What is affected?
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