CVE-2026-96951
Microsoft Windows Command Injection Vulnerability
Description
CVE-2026-96951 is a high-severity command injection vulnerability in Windows Shell that allows an unauthorized attacker to bypass a security feature over a network. Special elements in input processed by the shell are not properly neutralized, so content delivered to a user — Microsoft lists Outlook Web among the affected surfaces — can cause the shell to act on injected command structure instead of treating it as data, defeating a protection that is supposed to stop exactly that. Exploitation requires user interaction, which in practice means a user opening or interacting with attacker-supplied content, but no privileges on the target. CISA has added CVE-2026-96951 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and its remediation deadline of October 16, 2026 has already passed.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| microsoft | outlook web | - |
| microsoft | windows 10 1607 | < 10.0.14393.9612 |
| microsoft | windows 10 1809 | < 10.0.17763.9376 |
| microsoft | windows 10 21h2 | < 10.0.19044.7807 |
| microsoft | windows 10 22h2 | < 10.0.19045.7807 |
| microsoft | windows 11 23h2 | < 10.0.22631.7652 |
| microsoft | windows 11 24h2 | < 10.0.26100.9711 |
| microsoft | windows 11 25h2 | < 10.0.26200.9711 |
| microsoft | windows 11 26h1 | < 10.0.28000.3231 |
| microsoft | windows 11 26h2 | < 10.0.26300.9711 |
| microsoft | windows server 2012 | r2 |
| microsoft | windows server 2016 | < 10.0.14393.9612 |
| microsoft | windows server 2019 | < 10.0.17763.9376 |
| microsoft | windows server 2022 | < 10.0.20348.5761 |
| microsoft | windows server 2025 | < 10.0.26100.33650 |
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96951(Patch, Vendor Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96951(US Government Resource)
Weakness Type
CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Command injection occurs when software assembles a command from externally influenced input and fails to neutralize the special elements that change what that command does, so attacker-supplied text is interpreted as command structure. In Windows Shell this failure allows content that reaches the shell over a network path to subvert the intended command and bypass the security feature that would otherwise block it.
Learn more: CWE-77 — Improper Neutralization of Special Elements used in a Command ('Command Injection')
Impact Analysis
CVE-2026-96951 has a CVSS 3.1 base score of 8.8 (High) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Attack Vector (Network) and Privileges Required (None): the attacker delivers content remotely and needs no account on the target system, so any Windows client that receives files or links from outside is in scope. User Interaction (Required) is the single mitigating metric — a user must open or interact with the malicious content — but that is a routine action in an email or web workflow, not a high barrier, and the fact that the flaw bypasses a security feature means the warning or block the user would normally rely on does not appear. Attack Complexity (Low) and the absence of any special configuration make exploitation reliable. Confidentiality, Integrity and Availability (all High): injected commands run in the user's context, giving access to that user's data, the ability to modify it, and a foothold for further escalation on the host and into the domain. Given the enormous installed base — Windows 10, Windows 11 and Windows Server 2012 R2 through 2025 — and an EPSS score of 1.51% in the 75th percentile, this patch belongs in the current cycle, not the next one.
Exploit Maturity
CISA has added CVE-2026-96951 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of October 16, 2026 has already passed; the entry does not flag use in ransomware campaigns. The references are the Microsoft MSRC advisory and patch and the CISA catalog entry, so no public proof-of-concept appears in the reference set. The EPSS score of 1.51% places the vulnerability in the 75th percentile, above the median and consistent with a client-side flaw that is already being used. Security feature bypasses in Windows Shell are a well-established component of phishing chains, because they remove the warning or block that would otherwise interrupt the user; the practical expectation is therefore that this is delivered as part of a broader payload chain rather than exploited in isolation. Treat it as an active client-side threat across the whole Windows estate.
Remediation
- Carry out the action CISA requires, without delay. Apply mitigations in accordance with Microsoft's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of October 16, 2026 has already passed.
- Install the Microsoft security update for your Windows build. The fixed builds per release are given in the MSRC update guide entry for CVE-2026-96951 — for example 10.0.19045.7807 for Windows 10 22H2, 10.0.26100.9711 for Windows 11 24H2, 10.0.20348.5761 for Windows Server 2022 and 10.0.26100.33650 for Windows Server 2025. Windows Server 2012 R2 and the older Windows 10 servicing branches are affected as well.
- Verify deployment coverage rather than assuming it. Because the vulnerability spans many Windows versions, confirm patch status per build through your management system, and give priority to systems whose users routinely open external content: client workstations, terminal servers and virtual desktop hosts.
- Reduce the chance that malicious content reaches a user. Strengthen email and web content filtering so that the file types involved in shell handling are inspected or blocked at the gateway, and ensure users cannot be the last line of defence for a flaw that specifically bypasses the security feature meant to warn them.
- Watch for exploitation attempts and harden execution. Review endpoint detection telemetry for shell processes spawning unexpected children shortly after a document, archive or link is opened, and apply application control, attack surface reduction rules and least-privilege accounts, so that execution in a user context does not translate into a compromise of the whole machine.
Technical Details
The flaw sits in Windows Shell, the component that resolves and launches items the user interacts with, and consists of improper neutralization of special elements in a command that the shell constructs — CWE-77. When input carrying such elements reaches the shell over a network path, the elements are parsed as command structure rather than as literal text, and the resulting command is not the one the component intended to run. Microsoft characterizes the outcome as a security feature bypass, which is an important detail: the injected structure is used to circumvent a protection that would normally stop untrusted content from being acted upon, so the usual user-facing safeguard does not fire. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H places the attack over the network with no privileges, requiring only that the user interact with the content, and records full confidentiality, integrity and availability impact within an unchanged scope — the attacker gains the authority of the user whose shell processed the input.
Frequently Asked Questions
Is CVE-2026-96951 being actively exploited?
Yes. CISA has added CVE-2026-96951 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of October 16, 2026 has already passed. Use in ransomware campaigns is not recorded in the KEV entry, and the EPSS score of 1.51% places the vulnerability in the 75th percentile for exploitation likelihood.
What products are affected by CVE-2026-96951?
CVE-2026-96951 affects Windows Shell across Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2) and Windows Server 2012 R2, 2016, 2019, 2022 and 2025, each below the fixed build listed by Microsoft. Microsoft also lists Outlook Web among the affected surfaces, reflecting the delivery path for the malicious content.
How do I fix CVE-2026-96951?
Install the Microsoft security update for your Windows version as listed in the MSRC update guide for CVE-2026-96951 — for example build 10.0.19045.7807 on Windows 10 22H2 or 10.0.26100.9711 on Windows 11 24H2. Confirm coverage per build across the estate, prioritize systems whose users open external content, and strengthen gateway filtering in the meantime, since the vulnerability bypasses the security feature that would normally warn the user.
How severe is CVE-2026-96951?
CVE-2026-96951 is rated High with a CVSS 3.1 base score of 8.8: network-delivered, no privileges required, and full impact on confidentiality, integrity and availability in the user's context, with user interaction as the only barrier. Its EPSS score of 1.51% sits in the 75th percentile. The combination of a very large affected installed base and a bypass of the protection users rely on makes this more urgent than the base score alone suggests.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.