CVE-2026-96951
HIGHCISA KEVEPSS 74th pctlDescription
Improper neutralization of special elements used in a command ('command injection') in Windows Shell allows an unauthorized attacker to bypass a security feature over a network.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
Exploit Intelligence
Elevated risk: more likely to be exploited than 74% of all known CVEs.
Microsoft Windows Command Injection Vulnerability
Microsoft Windows Shell contains a command injection vulnerability that allows an unauthorized attacker to bypass a security feature over a network.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Remediation due: 2026-10-16
References
Related Vulnerabilities
Other CWE-77 (Command Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-3400 | Critical | 10.0 | 100% | KEV + Ransom | - |
| CVE-2024-21887 | Critical | 9.1 | 100% | KEV + Ransom | - |
| CVE-2023-1671 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2023-1389 | High | 8.8 | 100% | KEV | Fix |
| CVE-2021-1498 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2012-1823 | Critical | 9.8 | 100% | KEV | Fix |
Common questions
How do I fix CVE-2026-96951?
Published advisories record a fix for 20 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-96951 being actively exploited?
Yes. CVE-2026-96951 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2026-10-16. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2026-96951?
CVE-2026-96951 has a CVSS v3 base score of 8.8, rated important. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-96951 affect?
Published advisories record a fix for Windows 10 Version 1607 (Windows), Windows 10 Version 1809 (Windows), Windows 10 Version 21H2 (Windows), Windows 10 Version 22H2 (Windows), and 16 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-96951
Markdown
[](https://tridentstack.com/cve/CVE-2026-96951)HTML
<a href="https://tridentstack.com/cve/CVE-2026-96951"><img src="https://tridentstack.com/cve/badge/CVE-2026-96951.svg" alt="CVE-2026-96951"></a>This vulnerability is actively exploited in the wild
TridentStack Control detects known-exploited CVEs across your Windows fleet and prioritizes their patches. 200 endpoints free forever.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-16.