← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-96951 exploited? Yes: in CISA KEV since 13 Oct 2026

Gociux · Microsoft Windows · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-96951, Microsoft Windows Command Injection Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 13 Oct 2026, the day it was published. It affects Microsoft Windows. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 13 Oct 2026
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity8.8CVSS 3.1 · high
US federal due16 Oct 2026BOD 22-01 deadline

What it is

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

VendorMicrosoft (391 exploited CVEs in KEV)
ProductWindows
VulnerabilityMicrosoft Windows Command Injection Vulnerability
WeaknessCWE-77
Published13 Oct 2026
Added to KEV13 Oct 2026
Reported by (CNA)microsoft

What to do

  1. Check whether you run it. Look for Windows in your asset inventory, including appliances and cloud images. Stack check lists every exploited Microsoft CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 13 Oct 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for Microsoft.

Other exploited CVEs in Windows

References

Questions

Is CVE-2026-96951 being exploited?

Yes. CISA added CVE-2026-96951 to the Known Exploited Vulnerabilities catalog on 13 Oct 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-96951 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-96951?

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. Check Microsoft's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Windows and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in October 2026 · Microsoft scorecard · act-now radar.

Running Microsoft in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →