Skip to main content
CVE-2023-38160VulnerabilityPublished Updated

CVE-2023-38160: Microsoft Windows 10 Version 1809 · Use After Free

Affects Microsoft Windows 10 Version 1809Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

Affected software

ProductAffectedFixed in
Microsoft Windows 10 Version 1809Affected
  • =10.0.17763.0
Fixed in–

AI-suggested

1. Upgrade affected systems to a supported and patched version of Windows, preferably Windows 10 versions later than 1809 or Windows 11, as Microsoft no longer supports 1809 with security updates. 2. Restrict local access to critical systems by enforcing strict access controls, including the use of least privilege principles and strong authentication mechanisms. 3. Monitor and audit local user activities on systems running Windows 10 1809 to detect any suspicious behavior that could indicate exploitation attempts. 4. Employ endpoint detection and response (EDR) solutions capable of identifying anomalous memory access patterns or exploitation attempts related to use-after-free vulnerabilities. 5. Isolate legacy systems from sensitive network segments to limit the potential impact of information disclosure. 6. Educate internal users about the risks of local privilege misuse and enforce policies to prevent unauthorized software installation or execution. 7. Stay informed about Microsoft’s security advisories for any forthcoming patches or workarounds addressing this vulnerability.

Description

Windows TCP/IP Information Disclosure Vulnerability

References

Community reviews

Loading reviews…