CVE-2026-96951: Microsoft Windows Command Injection Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by microsoft, published 2026-10-13).

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

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since
2026-10-13
US federal deadline
2026-10-16
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-16527, EUVD-2026-100274, GHSA-hjr5-mppg-mjq7

VEDAS cluster: VEDAS:BARNACLEBLASTER

Exploit Observer has no public exploit code that names this CVE or one of its aliases.

Research and write-ups (3)

Vulnerability databases and vendor advisories (6)

Catalogue entries, not exploit evidence.

News (1)

118 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.098
some chance of attack soon
VEDAS
0.969
strong exploit evidence
On CISA KEV
Yes, since 2026-10-13
Detection rule
None yet
EPSS (chance of attack)
100.1CVE-2026-96951 EPSS over time2026-102026-11-01
VEDAS (exploit evidence)
100.9CVE-2026-96951 VEDAS over time2026-102026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Microsoft Microsoft Edge (Chromium-based)from 1.0.0.0 before 154.0.4258.62Not stated
Microsoft Outlook.comfrom 1.0.0 before 20260925.100Not stated
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.9612Not stated
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.9376Not stated
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.7807Not stated
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.7807Not stated
Microsoft Windows 11 version 23H2from 10.0.22631.0 before 10.0.22631.7652Not stated
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.7652Not stated
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.9711Not stated
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.9711Not stated
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.3231Not stated
Microsoft Windows 11 Version 26H2from 10.0.26300.0 before 10.0.26300.9711Not stated
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.23470Not stated
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.23470Not stated
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.9612Not stated
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.9612Not stated
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.9376Not stated
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.9376Not stated
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.5761Not stated
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.33650Not stated

1 more products are listed in the CVE record.

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: microsoft outlook_web, microsoft windows_10_1607, microsoft windows_10_1809, microsoft windows_10_21h2, microsoft windows_10_22h2, microsoft windows_11_23h2, microsoft windows_11_24h2, microsoft windows_11_25h2, microsoft windows_11_26h1, microsoft windows_11_26h2.

How to fix it

Fixed versions stated in the CVE record: 154.0.4258.62, 20260925.100, 10.0.14393.9612, 10.0.17763.9376, 10.0.19044.7807, 10.0.19045.7807, 10.0.22631.7652, 10.0.26100.9711, 10.0.26200.9711, 10.0.28000.3231, 10.0.26300.9711, 6.3.9600.23470 and others.

CISA required action: 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.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

References

Vendor advisories and patches

Government sources

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.