# CVE-2026-96951: Microsoft Windows Command Injection

> An attacker can bypass security features in Windows Shell via command injection, affecting Windows OS and Outlook.com users.

- **Severity:** High 8.8 (`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`)
- **Exploited in the wild:** Yes, since 13 Oct 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hjr5-mppg-mjq7

## What is CVE-2026-96951?

CVE-2026-96951 is a high-severity vulnerability in Microsoft Windows 10 1607, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-96951?

It affects 15 products.


Products: Microsoft Outlook Web, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows 11 26h1, Microsoft Windows 11 26h2, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2025.

## How do I fix CVE-2026-96951?

No fix has been published for CVE-2026-96951 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 16 Oct 2026.

## Is CVE-2026-96951 being exploited?

Yes. Attackers have exploited CVE-2026-96951 in the wild since at least 13 Oct 2026.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96951 and fix it if it is affected.

What it is: CVE-2026-96951 is a high-severity vulnerability in Microsoft Windows 10 1607, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2026-96951 in the wild since at least 13 Oct 2026.

Affected product: Microsoft Windows 10 1607. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96951/ (Markdown: https://insights.sbomify.com/CVE-2026-96951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96951
- OSV: https://osv.dev/vulnerability/CVE-2026-96951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96951/
Summaries are generated and may contain mistakes; the official description above is the record.