Skip to main content
CVE-2025-53805VulnerabilityPublished Updated

CVE-2025-53805: Microsoft Windows 11 version 22H2 · Out-of-bounds Read

Affects Microsoft Windows 11 version 22H2Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

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

  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 11 version 22H2Affected
  • =10.0.22621.0
Fixed in–

AI-suggested

Until official patches are released, organizations should implement the following mitigations: 1) Restrict network exposure of IIS servers by limiting inbound traffic to trusted IP addresses and networks using firewalls and network access controls. 2) Employ web application firewalls (WAFs) to detect and block suspicious or malformed requests targeting IIS. 3) Monitor IIS logs and network traffic for unusual patterns or repeated requests that could indicate exploitation attempts. 4) Consider temporarily disabling or isolating IIS services on Windows 11 22H2 systems if feasible, especially in high-risk environments. 5) Keep Windows and IIS updated with the latest security patches as soon as Microsoft releases a fix for this vulnerability. 6) Conduct regular vulnerability scanning and penetration testing to identify exposure. 7) Implement robust incident response plans to quickly address potential DoS incidents. These targeted steps go beyond generic advice by focusing on network-level controls and proactive monitoring specific to IIS and Windows 11 22H2 environments.

Description

Out-of-bounds read in Windows Internet Information Services allows an unauthorized attacker to deny service over a network.

References

Community reviews

Loading reviews…