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.
CVE-2018-8414
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 74%
- EPSS %ILE
- 99%
- KEV
- ⚠ Exploited
Published
August 15, 2018
Last Modified
October 28, 2025
Advisory Details (4)
Auto-updated Jun 2, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-8414Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8414Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 100× in last 7d / 375× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,113 total refreshes for this CVE.
- 2026-08-21 19:17 UTCGHSA enrichment
- 2026-08-21 16:49 UTCCISA KEV update
- 2026-08-21 15:40 UTCGHSA enrichment
- 2026-08-21 12:03 UTCVendor advisory
- 2026-08-21 12:03 UTCGHSA enrichment
- 2026-08-21 08:26 UTCVendor advisory
- 2026-08-21 08:26 UTCGHSA enrichment
- 2026-08-21 04:49 UTCVendor advisory
- 2026-08-21 04:49 UTCGHSA enrichment
- 2026-08-21 01:11 UTCEG score recompute
- 2026-08-21 01:11 UTCVendor advisory
- 2026-08-21 01:11 UTCGHSA enrichment
- 2026-08-20 22:51 UTCEPSS rescore
- 2026-08-20 21:34 UTCVendor advisory
- 2026-08-20 21:34 UTCGHSA enrichment
- 2026-08-20 17:58 UTCVendor advisory
- 2026-08-20 17:58 UTCGHSA enrichment
- 2026-08-20 17:06 UTCCISA KEV update
- 2026-08-20 14:21 UTCVendor advisory
- 2026-08-20 14:21 UTCGHSA enrichment
- 2026-08-20 10:45 UTCVendor advisory
- 2026-08-20 10:45 UTCGHSA enrichment
- 2026-08-20 07:08 UTCVendor advisory
- 2026-08-20 07:08 UTCGHSA enrichment
- 2026-08-20 03:32 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-19 23:55 UTCVendor advisory
- 2026-08-19 23:55 UTCGHSA enrichment
- 2026-08-19 20:18 UTCEG score recompute
- 2026-08-19 20:18 UTCVendor advisory
- 2026-08-19 20:18 UTCGHSA enrichment
- 2026-08-19 17:33 UTCCISA KEV update
- 2026-08-19 17:00 UTCEPSS rescore
- 2026-08-19 16:41 UTCVendor advisory
- 2026-08-19 16:40 UTCGHSA enrichment
- 2026-08-19 13:03 UTCVendor advisory
- 2026-08-19 13:03 UTCGHSA enrichment
- 2026-08-19 09:21 UTCVendor advisory
- 2026-08-19 09:21 UTCGHSA enrichment
- 2026-08-19 05:43 UTCVendor advisory
- 2026-08-19 05:43 UTCGHSA enrichment
- 2026-08-19 02:06 UTCVendor advisory
- 2026-08-19 02:06 UTCGHSA enrichment
- 2026-08-18 22:29 UTCGHSA enrichment
- 2026-08-18 18:53 UTCVendor advisory
- 2026-08-18 18:53 UTCGHSA enrichment
- 2026-08-18 16:58 UTCCISA KEV update
- 2026-08-18 15:15 UTCVendor advisory
- 2026-08-18 15:15 UTCGHSA enrichment
- 2026-08-18 11:39 UTCVendor advisory
- 2026-08-18 11:39 UTCGHSA enrichment
- 2026-08-18 08:02 UTCGHSA enrichment
- 2026-08-18 04:22 UTCGHSA enrichment
- 2026-08-18 00:45 UTCVendor advisory
- 2026-08-18 00:45 UTCGHSA enrichment
- 2026-08-17 21:06 UTCVendor advisory
- 2026-08-17 21:05 UTCGHSA enrichment
- 2026-08-17 17:29 UTCVendor advisory
- 2026-08-17 17:28 UTCGHSA enrichment
- 2026-08-17 13:56 UTCCISA KEV update
- 2026-08-17 13:51 UTCGHSA enrichment
- 2026-08-17 10:14 UTCVendor advisory
- 2026-08-17 10:14 UTCGHSA enrichment
- 2026-08-17 06:38 UTCVendor advisory
- 2026-08-17 06:38 UTCGHSA enrichment
- 2026-08-17 03:02 UTCVendor advisory
- 2026-08-17 03:02 UTCGHSA enrichment
- 2026-08-16 23:25 UTCVendor advisory
- 2026-08-16 23:25 UTCGHSA enrichment
- 2026-08-16 19:48 UTCVendor advisory
- 2026-08-16 19:48 UTCGHSA enrichment
- 2026-08-16 16:11 UTCVendor advisory
- 2026-08-16 16:11 UTCGHSA enrichment
- 2026-08-16 12:34 UTCVendor advisory
- 2026-08-16 12:34 UTCGHSA enrichment
- 2026-08-16 08:57 UTCVendor advisory
- 2026-08-16 08:57 UTCGHSA enrichment
- 2026-08-16 05:20 UTCEG score recompute
- 2026-08-16 05:20 UTCVendor advisory
- 2026-08-16 05:20 UTCGHSA enrichment
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-16 01:44 UTCVendor advisory
- 2026-08-16 01:44 UTCGHSA enrichment
- 2026-08-15 22:07 UTCVendor advisory
- 2026-08-15 22:07 UTCGHSA enrichment
- 2026-08-15 18:30 UTCVendor advisory
- 2026-08-15 18:30 UTCGHSA enrichment
- 2026-08-15 14:53 UTCVendor advisory
- 2026-08-15 14:53 UTCGHSA enrichment
- 2026-08-15 11:16 UTCVendor advisory
- 2026-08-15 11:16 UTCGHSA enrichment
- 2026-08-15 07:39 UTCVendor advisory
- 2026-08-15 07:39 UTCGHSA enrichment
- 2026-08-15 04:02 UTCEG score recompute
- 2026-08-15 04:02 UTCVendor advisory
- 2026-08-15 04:02 UTCGHSA enrichment
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-15 00:25 UTCVendor advisory
- 2026-08-15 00:25 UTCGHSA enrichment
- 2026-08-14 20:48 UTCVendor advisory
- 2026-08-14 20:48 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCwhereisr0da/CVE-2018-8414-POCFirst seen Aug 24, 2018
Simple poc of CVE-2018-8414 Windows Package Setting RCE Vulnerability
Open source ↗
Frequently asked(6)
What is CVE-2018-8414?
When was CVE-2018-8414 disclosed?
Is CVE-2018-8414 actively exploited?
What is the CVSS score of CVE-2018-8414?
Which products are affected by CVE-2018-8414?
How do I remediate CVE-2018-8414?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2018-8414
Is Your Infrastructure Affected by CVE-2018-8414?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.