CVE-2023-38149: Microsoft Windows 10 Version 1809 · Uncontrolled Resource Consumption
Affects Microsoft Windows 10 Version 1809Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 4.4% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 12 Sep 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1809 | Affected
| Fixed in– |
AI-suggested
1. Verify and apply any available security patches or updates from Microsoft for Windows 10 Version 1809. If patches are not yet available, consider upgrading affected systems to a supported Windows version with ongoing security updates. 2. Implement network-level filtering to block or rate-limit suspicious or malformed TCP/IP traffic that could trigger the vulnerability. 3. Deploy intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics capable of detecting anomalous network traffic patterns indicative of resource exhaustion attacks. 4. Monitor system performance and network traffic for signs of resource exhaustion or denial of service conditions, enabling rapid detection and response. 5. Segment networks to isolate legacy Windows 10 Version 1809 systems from untrusted or public networks, reducing exposure to remote attacks. 6. Conduct regular vulnerability assessments and penetration testing focused on legacy systems to identify and remediate exposure. 7. Educate IT and security teams about the vulnerability to ensure timely response and mitigation efforts. 8. Develop and test incident response plans specifically addressing denial of service scenarios impacting critical Windows hosts.
Description
Windows TCP/IP Denial of Service Vulnerability