CVE-2026-97798: CVE-2026-97798: Improper neutralization of argument delimiters in a command ('argument injection') in Wind…

CVE-2026-97798 at a glance

CVE-2026-97798 is a high-severity Argument Injection vulnerability in Microsoft Windows 10 21h2, with a CVSS 3.1 base score of 7.8. NVD published it on 2026-10-14 and classifies the weakness as CWE-88. Public exploit code: 2 public GitHub proof-of-concept repositories from 2 accounts, with the earliest exploit evidence dated 2026-10-27. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.37% (percentile 30.9, scored 2026-11-03). NVD configuration data lists a fixed release for 9 products, for example microsoft windows 10 21h2 10.0.19044.7807. Its CVERadar threat level is 43/100.

What it is

Improper neutralization of argument delimiters in a command ('argument injection') in Windows Error Reporting allows an authorized attacker to elevate privileges locally.

Exploitation evidence

First exploit evidence seen: 2026-10-27 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

2 public repositories from 2 accounts, first seen 2026-10-27. Most starred: G4sp4rCS/CVE-2026-97798-exploit (41 stars), view the G4sp4rCS/CVE-2026-97798-exploit repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

Patches, mitigations and detection

Fixed versions

• microsoft windows 10 21h2: upgrade to 10.0.19044.7807 or later
• microsoft windows 10 22h2: upgrade to 10.0.19045.7807 or later
• microsoft windows 11 23h2: upgrade to 10.0.22631.7652 or later
• microsoft windows 11 24h2: upgrade to 10.0.26100.9711 or later
• microsoft windows 11 25h2: upgrade to 10.0.26200.9711 or later
• microsoft windows 11 26h1: upgrade to 10.0.28000.3231 or later
• microsoft windows 11 26h2: upgrade to 10.0.26300.9711 or later
• microsoft windows server 2022: upgrade to 10.0.20348.5761 or later
• microsoft windows server 2025: upgrade to 10.0.26100.33650 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• Microsoft vendor advisory (msrc.microsoft.com) (Patch, Vendor Advisory)

Detection Generic guidance

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Businesses without a dedicated security person can have LayerLogix watch their computers for threats.