SECURITY_THREAT_PULSE
LIVE
LAST UPDATED
FIRST SEEN
7 SOURCES ON THIS EVENT
▲ ACT NOWCVE-2026-96951 · CVSS 8.8

Microsoft Windows: attackers can run commands on it

OFFICIAL NAME: Microsoft Windows Command Injection Vulnerability

WHAT IT IS · COMPUTERS, PHONES AND BROWSERSIt runs on staff computers, phones or browsers.

DO THIS FIRSTInstall the latest updates on every device, and turn on automatic updates. Not sure if you use it? Send this page to your IT provider or security lead and ask.

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

WHY THIS VERDICT Attacks are confirmed. The vulnerability is 28 days old, so many systems are likely still unpatched.

WHY IT RANKS HERE Exploitation is confirmed by an authoritative source. 12 products are affected.

HIGHEST CONFIRMED RUNG
EXPLOITED
CISA KEV
LISTED
EXPLOIT CODE
NONE KNOWN
// EVIDENCE LADDER

How far has it climbed?

CONFIRMED
REPORTED
NO EVIDENCE
  1. 01 TALK

    ■ CONFIRMED
    NEWEST EVIDENCE · 3 INDEPENDENT SOURCES

    CVE-2026-96951 discussed publicly (CIRCL sighting). CVE-2026-96951 discussed publicly (CIRCL sighting).

  2. 02 EXPOSED

    □ NOT TRACKED YET
    NO SOURCE FOR THIS STEP YET

    We have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.

  3. 03 TRIED

    ■ CONFIRMED
    NEWEST EVIDENCE · 3 INDEPENDENT SOURCES

    Attacks that worked are confirmed (step 4), so attempts count as confirmed too.

  4. 04 EXPLOITED

    ■ CONFIRMED
    NEWEST EVIDENCE · 3 INDEPENDENT SOURCES

    Microsoft confirms exploitation: Windows Shell Security Feature Bypass Vulnerability. CISA Vulnrichment marks CVE-2026-96951 as actively exploited.

  5. 05 DAMAGE

    □ NOT TRACKED YET
    NO SOURCE FOR THIS STEP YET

    Breach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.

// THE CLOCK

When each thing happened

  1. DISCLOSED
  2. EXPLOIT CODE PUBLIC
    NOT YET
  3. FIRST ATTACK REPORT
  4. CISA KEV LISTING
  5. US FEDERAL DEADLINE
Attacks were reported on or before the day the flaw was disclosed.

THE FIX

CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. The deadline CISA set for US federal agencies, Oct 16, 2026, has passed. It is a US government deadline; use it as a guide.

// ASK YOUR TEAM

Questions to ask this week

// TIMELINE · PACIFIC TIME

How it unfolded

  1. Attack activity. OCT 12, 2026
    Microsoft Windows Command Injection Vulnerability
  2. Attack activity. OCT 13, 2026
    CISA Vulnrichment marks CVE-2026-96951 as actively exploited
  3. OCT 13, 2026
    Microsoft Patches More Than 1,400 Security Flaws
  4. OCT 25, 2026
    CVE-2026-96951 discussed publicly (CIRCL sighting) (12 reports, latest NOV 7)
  5. Attack activity. OCT 26, 2026
    Microsoft confirms exploitation: Windows Shell Security Feature Bypass Vulnerability
  6. NOV 5, 2026
    November 2026 Patch Tuesday forecast: Old software continues to bite

SOURCES

  1. [1] CIRCL Vulnerability-Lookup sightings: CVE-2026-96951 discussed publicly (CIRCL sighting), NOV 7
  2. [2] Help Net Security: November 2026 Patch Tuesday forecast: Old software continues to bite, NOV 5
  3. [3] Microsoft Security Response Center: Microsoft confirms exploitation: Windows Shell Security Feature Bypass Vulnerability, OCT 26
  4. [4] Krebs on Security: Microsoft Patches More Than 1,400 Security Flaws, OCT 13
  5. [5] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-96951 as actively exploited, OCT 13
  6. [6] CISA Known Exploited Vulnerabilities: Microsoft Windows Command Injection Vulnerability, OCT 12
  7. [7] CIRCL Vulnerability-Lookup sightings: 11 more reports