CVE Intelligence
CISA KEV High Injection

CVE-2026-96951 — Microsoft Windows Command Injection Vulnerability

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.

Published Oct 13, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, CISA Known Exploited Vulnerabilities, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 1.5% (30-day exploitation probability)+11
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Oct 13, 2026
EPSS FIRST
1.51%
ahead of 74% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Outlook Web and 29 more
CVSS base
8.8
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

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.

US federal deadline: Oct 16, 2026 — due in 1 day(s)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Outlook Web, Microsoft Outlook.com, Microsoft Windows 10 1607…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  6. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Outlook Web versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Outlook.com ≥ 1.0.0 and < 20260925.100 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 1607 < 10.0.14393.9612 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1809 < 10.0.17763.9376 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 21h2 < 10.0.19044.7807 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 22h2 < 10.0.19045.7807 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 Version 1607 ≥ 10.0.14393.0 and < 10.0.14393.9612 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 1809 ≥ 10.0.17763.0 and < 10.0.17763.9376 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 21H2 ≥ 10.0.19044.0 and < 10.0.19044.7807 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 22H2 ≥ 10.0.19045.0 and < 10.0.19044.7807 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 23h2 < 10.0.22631.7652 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 24h2 < 10.0.26100.9711 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 25h2 < 10.0.26200.9711 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 26h1 < 10.0.28000.3231 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 26h2 < 10.0.26300.9711 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 version 23H2 ≥ 10.0.22631.0 and < 10.0.22631.7652 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 Version 24H2 ≥ 10.0.26100.0 and < 10.0.26100.9711 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 Version 25H2 ≥ 10.0.26200.0 and < 10.0.26200.9711 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 version 26H1 ≥ 10.0.28000.0 and < 10.0.28000.3231 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 Version 26H2 ≥ 10.0.26300.0 and < 10.0.26300.9711 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2012 version r2 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2012 R2 ≥ 6.3.9600.0 and < 6.3.9600.23470 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2012 R2 (Server Core installation) ≥ 6.3.9600.0 and < 6.3.9600.23470 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2016 ≥ 10.0.14393.0 and < 10.0.14393.9612 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2016 < 10.0.14393.9612 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2016 (Server Core installation) ≥ 10.0.14393.0 and < 10.0.14393.9612 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 ≥ 10.0.17763.0 and < 10.0.17763.9376 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 < 10.0.17763.9376 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2019 (Server Core installation) ≥ 10.0.17763.0 and < 10.0.17763.9376 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2022 < 10.0.20348.5761 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2022 ≥ 10.0.20348.0 and < 10.0.20348.5761 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2025 ≥ 10.0.26100.0 and < 10.0.26100.33650 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2025 < 10.0.26100.33650 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2025 (Server Core installation) ≥ 10.0.26100.0 and < 10.0.26100.33650 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 secure@microsoft.com via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High — — microsoft via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: secure@microsoft.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-77 · Command Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Oct 13, 2026
Federal deadline
Oct 16, 2026
due in 1 day(s)
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Oct 13, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products removed · 1
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/outlook web
    Oct 14, 2026 · NIST National Vulnerability Database
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/outlook, microsoft/windows 10 1607, microsoft/windows 10 1809, microsoft/windows 10 21h2, microsoft/windows 10
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · Undergoing Analysis → Analyzed
    Oct 14, 2026 · NIST National Vulnerability Database
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Source status changed · Awaiting Analysis → Undergoing Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/outlook.com, microsoft/windows 10 version 1607, microsoft/windows 10 version 1809, microsoft/windows 10 versio
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 13, 2026 · microsoft
  • Added to CISA KEV catalog
    Oct 12, 2026 · CISA

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2026-10
what else CISA listed that month
Injection
same class
CWE-77
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 1d
  • Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 1d
  • Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 1d
  • Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 1d
  • Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 1d
  • Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-96951 is "Microsoft Windows Command Injection Vulnerability", rated High. It affects Outlook Web (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 1.51% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.