DE EN IT

~/exploited / cve-2026-96951

CVE-2026-96951: Microsoft Windows

According to CISA this vulnerability is already used in attacks (added on 13 October 2026).

Key facts

CVECVE-2026-96951
VendorMicrosoft — Windows
VulnerabilityMicrosoft Windows Command Injection Vulnerability
Added13 October 2026
Deadline (US agencies)16 October 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score8.8 (high) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attack over the network, complexity: low, privileges: none needed, user interaction: required
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 9.81%. Higher than 95.6% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-77 — Command Injection
Affected versionswindows 10 1607: < 10.0.14393.9612
windows 10 1809: < 10.0.17763.9376
windows 10 21h2: < 10.0.19044.7807
windows 10 22h2: < 10.0.19045.7807
windows 11 23h2: < 10.0.22631.7652
windows 11 24h2: < 10.0.26100.9711
windows 11 25h2: < 10.0.26200.9711
windows 11 26h1: < 10.0.28000.3231
and 6 more

Description (NVD)

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.

Patches and vendor advisories

Description (CISA)

Microsoft Windows Shell contains a command injection vulnerability that allows an unauthorized attacker to bypass a security feature over a network.

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.

What admins should do now

  1. Affected? Check whether Microsoft Windows is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 13 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).