Skip to main content
VulnerabilityPublished Updated

CVE-2022-35769: Microsoft Windows 10 Version 1809 · Denial of Service

Affects Microsoft Windows 10 Version 1809Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.4% chance of exploitation in 30 days – higher than 84% 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:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Aug 2022

  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 26 Oct 2026.

What to do

Affected software

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

AI-suggested

Given the lack of an official patch linked in the provided data, European organizations should prioritize the following mitigations: 1) Upgrade or migrate systems from Windows 10 Version 1809 to a supported and patched Windows version to eliminate exposure to this vulnerability. 2) Restrict or monitor PPP traffic at network boundaries using firewalls or intrusion prevention systems to detect and block malformed or suspicious PPP packets. 3) Implement network segmentation to isolate legacy systems running vulnerable versions, limiting exposure to untrusted networks. 4) Employ robust network monitoring and anomaly detection to identify unusual traffic patterns indicative of exploitation attempts. 5) Develop and test incident response plans specifically addressing DoS scenarios to minimize downtime impact. 6) Engage with Microsoft support channels to obtain any out-of-band patches or workarounds if available. 7) Educate IT and security teams about the vulnerability and ensure asset inventories accurately identify affected systems for targeted remediation.

Description

Windows Point-to-Point Protocol (PPP) Denial of Service Vulnerability

References

Community reviews

Loading reviews…