SAK T.E.CTechnology · Evaluation · Compliance Free domain checkCheck

Exploited vulnerabilities / CVE-2026-96951

Confirmed exploited · command injection · Microsoft Windows

CVE-2026-96951

Microsoft Windows command injection, confirmed exploited in the wild.

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

9.8%chance of exploitation in the next 30 days (EPSS), 95th percentile
13 Octadded to CISA's Known Exploited Vulnerabilities list, 2026
16 Octfederal remediation deadline, already passed
Passedpast the deadline: patch now
CISA's name for itMicrosoft Windows Command Injection Vulnerability
Vendor and productMicrosoft · Windows
Typecommand injection · CWE-77
ExploitedConfirmed by CISA listed 13 October 2026
Likelihoodone of the most likely to be exploited of every vulnerability tracked
Deadline16 October 2026 · already passed
Used in ransomwareNot reported
Advisoriesmsrc.microsoft.com ↗ · nvd.nist.gov ↗
What to do

Three steps, in this order

Step 1

Apply the vendor fix; command injection on an exposed device is used within days of disclosure.

Step 2

Restrict the management interface to a trusted network until the fix is in.

Step 3

Review the device's logs and configuration for changes you did not make.

CISA's required actionApply 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.
Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Questions

CVE-2026-96951 in short

Is CVE-2026-96951 being exploited?

Yes. CISA added CVE-2026-96951 to its Known Exploited Vulnerabilities catalogue on 13 October 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-96951?

US federal agencies must remediate it by 16 October 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-96951 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 9.8%, the 95th percentile of every CVE it scores.

How do I fix CVE-2026-96951?

Apply the vendor fix; command injection on an exposed device is used within days of disclosure. Restrict the management interface to a trusted network until the fix is in. Review the device's logs and configuration for changes you did not make.

Same vendor

Other Microsoft vulnerabilities being exploited

CVEProductTypeListed
CVE-2026-124194Officeexploited vulnerability10 November 2026
CVE-2026-65660SharePointexploited vulnerability25 September 2026
CVE-2026-81963Windowsprivilege escalation8 September 2026
CVE-2026-85880Windowsprivilege escalation8 September 2026
CVE-2019-1068SQL Serverremote code execution26 August 2026
CVE-2026-33824Internet Key Exchange (IKE) Service Extensionsremote code execution18 August 2026

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.

Chat with us