CVE-2025-55698: Microsoft Windows 11 Version 24H2 · NULL Pointer Dereference
Affects Microsoft Windows 11 Version 24H2Source CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 11 Version 24H2 | Affected
| Fixed in– |
AI-suggested
1. Monitor Microsoft security advisories closely and apply official patches or updates as soon as they are released to remediate the vulnerability. 2. Restrict network access to systems running Windows 11 24H2, especially limiting access to DirectX-related services or components where feasible. 3. Implement network segmentation and firewall rules to reduce the attack surface and prevent unauthorized internal or external access. 4. Employ intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous DirectX or related traffic patterns that could indicate exploitation attempts. 5. Enforce the principle of least privilege to limit the ability of attackers with authorized access to exploit the vulnerability. 6. Conduct regular system and application monitoring to detect crashes or instability that may indicate exploitation attempts. 7. Prepare incident response plans to quickly isolate and recover affected systems in case of denial of service events. 8. Consider temporary workarounds such as disabling or restricting DirectX features if feasible and if patches are not yet available, after evaluating operational impact. 9. Educate IT staff about the vulnerability specifics to ensure rapid recognition and response. These measures go beyond generic advice by focusing on network-level controls, monitoring, and privilege management tailored to the nature of this vulnerability.
Description
Null pointer dereference in Windows DirectX allows an authorized attacker to deny service over a network.