Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted file or link to user
-
DeliveryUser opens malicious content
-
ExploitBypass Windows Shell security feature
-
ExecutionInject and execute commands
-
ImpactFull host compromise (C/I/A)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires victim user interaction (CVSS UI:R): the target must open or interact with attacker-supplied content (e.g., a crafted file, shortcut, or link) that triggers the Windows Shell security-feature bypass and subsequent command injection. No authentication or prior privileges are needed (PR:N) and the vector is network-reachable (AV:N) with low complexity (AC:L), so no special target configuration is indicated - default Windows Shell behavior is affected. The primary limiting factor is the need for user interaction, which is why SSVC rates the flaw as not automatable; there is no evidence of a non-default configuration requirement. |
| Impact | This is a genuine top-tier priority, not a high-CVSS-but-low-risk case. Multiple independent signals converge: CISA KEV confirms active exploitation in the wild, SSVC rates exploitation as 'active' with 'total' technical impact, a patch is available, and the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) indicates a network-reachable, low-complexity, unauthenticated flaw with full confidentiality, integrity, and availability compromise. The only meaningful brake is UI:R - successful exploitation requires a victim to take an action (e.g., open a crafted file or follow a link) - which is consistent with SSVC marking Automatable='no', so exploitation is user-interaction-gated rather than wormable/mass-automatable. Note a semantic tension worth flagging: the description frames the issue as allowing an attacker to 'bypass a security feature,' yet the CWE is CWE-77 (command injection) and the impact metrics are a full C:H/I:H/A:H triad; the security-feature-bypass framing likely describes the mechanism (evading a Shell protection) that then enables code/command execution - verify exact exploitation primitive against Microsoft's MSRC advisory. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be compared here; however, KEV status makes EPSS moot for prioritization. Treat as emergency-patch class given confirmed active exploitation across virtually all supported Windows releases. |
| Exploit ScenarioDerived | An attacker delivers a crafted file, shortcut, or link to a target and, leveraging a Windows Shell security-feature bypass, causes command injection (CWE-77) when the victim opens or interacts with it. Because this is confirmed actively exploited (CISA KEV) with low attack complexity and no prior privileges, a single user click can yield full compromise of the host. No standalone public POC is identified in the provided data, but in-the-wild exploitation is confirmed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then execute arbitrary commands, yielding high impact to confidentiality, integrity, and availability. The attack is network-reachable with low complexity but requires victim interaction (CVSS UI:R) - the target must open or interact with attacker-supplied content such as a crafted file, shortcut, or link - which is why SSVC rates it non-automatable while still flagging total technical impact. The flaw affects Windows 10, Windows 11, and Windows Server 2012 R2 through 2025, plus Outlook.com, and is confirmed actively exploited (CISA KEV); given the KEV listing and the assessed high-end impact, this is a genuine top-tier patching priority rather than a high-CVSS-but-low-risk case.
RemediationAI
Patch status is Patch available per vendor advisory; Microsoft (secure@microsoft.com) has published remediation at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96951, and the EUVD version ranges indicate the fixed build thresholds to update to - for example 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.14393.9612 for Windows 10 1607 and Windows Server 2016, 10.0.17763.9376 for Windows 10 1809 and Windows Server 2019, 10.0.20348.5761 for Windows Server 2022, 6.3.9600.23470 for Windows Server 2012 R2, 10.0.26100.33650/10.0.26100.9711 for Windows Server 2025 and Windows 11 24H2, and 10.0.22631.7652, 10.0.26200.9711, 10.0.28000.3231 and 10.0.26300.9711 for the corresponding Windows 11 releases. Because this CVE is confirmed actively exploited (CISA KEV) and SSVC records active exploitation with total technical impact, treat it as emergency maintenance: apply the cumulative updates to all listed client, server, and Server Core builds, and ensure the Outlook.com service-side fix (build 20260925.100 or later) is deployed. Where immediate patching of every endpoint is not feasible, the exploit chain depends on a user opening attacker-supplied content, so compensating controls are to enforce Mark-of-the-Web and SmartScreen evaluation on all inbound files and email attachments, use mail/web gateways to strip or quarantine untrusted shortcut (.lnk), script, and archive/container formats, disable or restrict Windows Shell preview and handler functionality for untrusted file types, and enable Microsoft Defender Attack Surface Reduction rules that block shell-created child processes and Office/app execution of downloaded payloads. Trade-offs to weigh: blocking .lnk and archive attachments disrupts legitimate internal file-sharing workflows and will generate user complaints, and aggressive ASR/script-blocking rules can break line-of-business macros and installer scripts, so stage them in audit mode first; none of these workarounds remove the underlying command-injection path, and they become unnecessary once the vendor updates above are installed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-77, improper neutralization of special elements used in a command, i.e., classic command injection. The Windows Shell constructs and hands command strings to an interpreter without adequately escaping or validating attacker-influenced data, so crafted content processed by the shell is interpreted as command syntax rather than inert data. Because the vulnerable path sits in the Shell itself, the injection also lets an attacker bypass a Windows security feature (the same parsing/trust path that is supposed to enforce that protection), turning a single user click into arbitrary code execution in the user's context. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H confirms the network-reachable, unauthenticated, low-complexity nature of the flaw, with the sole practical barrier being the user-interaction requirement; the scope remains unchanged, so the impact is contained to the vulnerable Shell component rather than escalating across security boundaries. Affected builds span the Windows 10, Windows 11, and Windows Server code bases (10.0.14393.x, 10.0.17763.x, 10.0.19044/19045.x, 10.0.20348.x, 10.0.22631.x, 10.0.26100.x, 10.0.26200.x, 10.0.26300.x, 10.0.28000.x, and the legacy 6.3.9600.x branch), which is consistent with a long-lived Shell parsing component shared across releases.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network-delivered, low-complexity, unauthenticated command injection requiring a victim click (UI:R), yielding full host compromise (C:H/I:H/A:H) within an unchanged scope.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
3DescriptionCVE.org
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.
Technical POC Analysis
Evidence caveat up front: the only primary source supplied is the CISA KEV entry (GCVE UUID ddbf6640-16e5-4ba6-87f2-6ad3daf81d63) plus the summary supplied with this task.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
A high-severity command-injection vulnerability in Microsoft Windows Shell (CVE-2026-96951) is confirmed actively exploited (CISA KEV) and affects Windows 10, Windows 11, Windows Server 2012 R2 through 2025, and Outlook.com. Although exploitation requires a user to open or interact with attacker-supplied content, it can bypass a Windows security feature and allow arbitrary command execution with high impact to confidentiality, integrity, and availability. This creates enterprise-wide risk of endpoint compromise, lateral movement, and data loss across both workstation/server estates and Outlook.com users, making immediate patching a top leadership priority.
Apply vendor patch.
Threat Model
5 threats: Elevation of Privilege, Tampering, Information Disclosure and 2 more
5-step attack chain with trust boundaries and controls
Full threat model - attack chain, trust boundaries, controls per stage and evidence - is part of the Pro and Business plans.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-100274
GHSA-hjr5-mppg-mjq7
NVD
CVE.org
CISA KEV
EPSS
Vulnrichment
VulDB
Exploit-DB