Microsoft Windows Command Injection
CVE-2026-96951 is a high-severity improper neutralization of special elements used in a command vulnerability in Microsoft Edge (Chromium-based) from Microsoft, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 154.0.4258.62 as the first without the flaw, so updating Microsoft Edge (Chromium-based) to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on October 13, 2026, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Microsoft Edge (Chromium-based) to 154.0.4258.62 or a later version.
- Update Outlook.com to 20260925.100 or a later version.
- Update Windows 10 Version 1607 to 10.0.14393.9612 or a later version.
- CISA's required action: 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.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Microsoft Edge (Chromium-based) | 1.0.0.0 up to, but not including, 154.0.4258.62 | 154.0.4258.62 |
| Microsoft | Outlook.com | 1.0.0 up to, but not including, 20260925.100 | 20260925.100 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.9612 | 10.0.14393.9612 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.7807 | 10.0.19044.7807 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.7807 | 10.0.19045.7807 |
| Microsoft | Windows 11 version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.7652 | 10.0.22631.7652 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.9711 | 10.0.26100.9711 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.9711 | 10.0.26200.9711 |
| Microsoft | Windows 11 version 26H1 | 10.0.28000.0 up to, but not including, 10.0.28000.3231 | 10.0.28000.3231 |
| Microsoft | Windows 11 Version 26H2 | 10.0.26300.0 up to, but not including, 10.0.26300.9711 | 10.0.26300.9711 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.23470 | 6.3.9600.23470 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.23470 | 6.3.9600.23470 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.9612 | 10.0.14393.9612 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.9612 | 10.0.14393.9612 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.5761 | 10.0.20348.5761 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.33650 | 10.0.26100.33650 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.33650 | 10.0.26100.33650 |
| Microsoft | Outlook Web | Not specified in the record | Not stated |
| Microsoft | Windows 10 1607 | before 10.0.14393.9612 | 10.0.14393.9612 |
| Microsoft | Windows 10 1809 | before 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.7807 | 10.0.19044.7807 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.7807 | 10.0.19045.7807 |
Version data comes from the organisation that assigned the CVE; 6 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
Timeline
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96951US Government Resource
Our coverage
Other vulnerabilities in Microsoft Edge (Chromium-based)
- 7.4 High severity
- 8.1 High severity
- 8.8 High severity
- 8.1 High severity
- 7.8 High severity
- 8.8 High severity
Recent Improper Neutralization of Special Elements used in a Command vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
- 10.0 Critical severity
- 9.9 Critical severity
- 9.9 Critical severity
Spotted an error? Tell us.