Microsoft Windows Shell Remote Code Execution Vulnerability
Microsoft · Windows
A remote code execution flaw in the Windows Shell component of Microsoft Windows arises because the shell does not properly validate file paths. An attacker who can get a user to interact with a crafted file or path, such as by opening or viewing it, could execute code on the affected system.
A remote code execution vulnerability exists when the Windows Shell does not properly validate file paths, aka "Windows Shell Remote Code Execution Vulnerability." This affects Windows 10 Servers, Windows 10.
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 1/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.How attackers get in
What they do
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 1 day before it was disclosed. Public exploit code (PoC-in-GitHub) appeared 9 days after disclosure.
- First seen exploitedVulnCheck KEV evidence1 day before
- Disclosedday 0
- Public exploit codePoC-in-GitHub+9 days
- Added to CISA KEVEU database agrees+4 yrs
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order, 2 cited passages 2ExecutionTA0002
Successful exploitation yields arbitrary code execution
remote code execution vulnerability exists when the Windows Shell
Malicious link or file opened by user triggers shell
A remote code execution vulnerability exists when the Windows Shell does not properly validate file paths
Lower-confidence links (3)
These come from early or generic mappings, text matching, or contradict this CVE’s details (for example a public-facing technique on a bug that needs a user to open a file). Shown for completeness.
- Exploit Public-Facing ApplicationT1190 needs user interaction; not a public-facing exploit
- Exploitation of Remote ServicesT1210 needs user interaction; not a public-facing exploit
- Application or System ExploitationT1499.004 CTID attack_to_cve Phase 1 "Uncategorized" mapping (not staged by impact)
Detection
0 rules for this CVE · 99 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2018-8414 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Malicious LinkT1204.0014 general rules
- Symlink Etc Passwdhightest
- Potential ClickFix Execution Pattern - Registryhighexperimental
- Suspicious ClickFix/FileFix Execution Patternhighexperimental
- Suspicious Execution via macOS Script Editormediumtest
Command and Scripting InterpreterT105995 general rules
- HackTool - Sliver C2 Implant Activity Patterncriticaltest
- Lazarus Group Activitycriticaltest
- REvil Kaseya Incident Malware Patternscriticaltest
- Turla Group Lateral Movementcriticaltest
- Windows Defender AMSI Trigger Detectedhighstable
- Windows Defender Threat Detectedhighstable
- Abusable DLL Potential Sideloading From Suspicious Locationhightest
- Add Insecure Download Source To Wingethightest
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Not named in any threat report yetAlso mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- Actively_Exploited_Kev | Oct 22, 202621 Oct 2026
- 44 more on OTX