Skip to content
Server Security Center
KEVhigh8.8

CVE-2026-96951: Microsoft Windows Command Injection

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2026-10-13.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
9.8%
higher than 95.6% of all CVEs
Added to CISA KEV
2026-10-13
US federal due date 2026-10-16
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-96951 explained

CVE-2026-96951 is a command injection vulnerability (CWE-77) in Windows Shell. An unauthorized attacker can use it to bypass a security feature over a network. It affects many Windows client and server versions, Microsoft Edge (Chromium-based) and Microsoft Outlook.com, and CISA lists it as known to be exploited.

Impact

An unauthenticated attacker can bypass a security feature over a network. Attack complexity is low and no privileges are needed, but a user must take some action for the attack to succeed. CISA rates the technical impact as total, meaning full control of the affected component or full disclosure of its information. CISA does not consider it automatable. Confidentiality, integrity and availability impacts are all high. Attackers are known to exploit it. Ransomware use is unknown.

Who is affected

Affected: Microsoft Edge (Chromium-based) before 154.0.4258.62. Microsoft Outlook.com before 20260925.100. Windows 10 1607 before 10.0.14393.9612, 1809 before 10.0.17763.9376, 21H2 before 10.0.19044.7807, 22H2 before 10.0.19045.7807. Windows 11 23H2 before 10.0.22631.7652, 24H2 before 10.0.26100.9711, 25H2 before 10.0.26200.9711, 26H1 before 10.0.28000.3231, 26H2 before 10.0.26300.9711. Windows Server 2012 R2 before 6.3.9600.23470. Each listed version is the fix. The page lists 8 further products.

Written with AI from the data on this page and checked against it automatically.

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.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Edge (Chromium-based)
    Affected
    • < 154.0.4258.62
    Fixed in
    • 154.0.4258.62
  • Microsoft Outlook.com
    Affected
    • < 20260925.100
    Fixed in
    • 20260925.100
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.9612
    Fixed in
    • 10.0.14393.9612
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.9376
    Fixed in
    • 10.0.17763.9376
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.7807
    Fixed in
    • 10.0.19044.7807
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.7807
    Fixed in
    • 10.0.19045.7807
  • Microsoft Windows 11 version 23H2ARM64, x64
    Affected
    • < 10.0.22631.7652
    Fixed in
    • 10.0.22631.7652
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.9711
    Fixed in
    • 10.0.26100.9711
  • Microsoft Windows 11 Version 25H2ARM64, x64
    Affected
    • < 10.0.26200.9711
    Fixed in
    • 10.0.26200.9711
  • Microsoft Windows 11 version 26H1ARM64, x64
    Affected
    • < 10.0.28000.3231
    Fixed in
    • 10.0.28000.3231
Show 10 more products
  • Microsoft Windows 11 Version 26H2ARM64, x64
    Affected
    • < 10.0.26300.9711
    Fixed in
    • 10.0.26300.9711
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.23470
    Fixed in
    • 6.3.9600.23470
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.23470
    Fixed in
    • 6.3.9600.23470
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.9612
    Fixed in
    • 10.0.14393.9612
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.9612
    Fixed in
    • 10.0.14393.9612
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.9376
    Fixed in
    • 10.0.17763.9376
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.9376
    Fixed in
    • 10.0.17763.9376
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.5761
    Fixed in
    • 10.0.20348.5761
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.33650
    Fixed in
    • 10.0.26100.33650
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.33650
    Fixed in
    • 10.0.26100.33650

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Edge (Chromium-based): 154.0.4258.62
    • Microsoft Outlook.com: 20260925.100
    • Microsoft Windows 10 Version 1607: 10.0.14393.9612
    • Microsoft Windows 10 Version 1809: 10.0.17763.9376
    • Microsoft Windows 10 Version 21H2: 10.0.19044.7807
    • Microsoft Windows 10 Version 22H2: 10.0.19045.7807
    Fixed versions for 14 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96951
  • CISA's deadline for US federal agencies: 2026-10-16 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security updates that bring each Windows system to the fixed build listed for its version.
  2. Update Microsoft Edge (Chromium-based) to 154.0.4258.62 or later.
  3. Review the Microsoft advisory for the further listed products and for any mitigations.
  4. Prioritize internet-exposed and user-facing systems, as CISA lists this vulnerability as known exploited.
  5. Check systems for signs of compromise, in line with CISA's forensics triage requirements.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

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

Questions about CVE-2026-96951

Is CVE-2026-96951 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-10-13. Whether it is used in ransomware campaigns is unknown.
What is the deadline for US federal agencies?
CISA set a due date of 2026-10-16. Agencies must apply vendor mitigations per BOD 26-04 or discontinue use of the product if mitigations are unavailable.
Does the attack need user action?
Yes. The CVSS data shows user interaction is required. No privileges or authentication are needed, and the attack works over a network.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.