CVE-2018-8414

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 73%CVSS: 8.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100

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 computed (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
73%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2018-8414

Published

August 15, 2018

Last Modified

October 28, 2025

Advisory Details (4)

Auto-updated Oct 12, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: microsoft, cisa.
CISA🔴 Active Exploitation

Known 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-8414
Microsoft

Security Update Guide - Microsoft Security Response Center

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8414
Web page

CVE-2018-8414 - PSIRT.COM

http://www.securityfocus.com/bid/105016
Web page
http://www.securitytracker.com/id/1041458

Vendor Advisories for CVE-2018-8414(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 92× in last 7d / 440× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 1,871 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 1,773 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 08:57 UTCVendor advisory
  2. 2026-10-13 08:57 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-12 20:07 UTCEG score recompute
  4. 2026-10-12 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
  5. 2026-10-12 08:18 UTCVendor advisory
  6. 2026-10-12 08:18 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-12 04:41 UTCVendor advisory
  8. 2026-10-12 04:40 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-10-12 01:00 UTCVendor advisory
  10. 2026-10-12 01:00 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-10-11 21:22 UTCEG score recompute
  12. 2026-10-11 21:22 UTCVendor advisory
  13. 2026-10-11 21:22 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-11 17:42 UTCEG score recompute
  15. 2026-10-11 17:42 UTCVendor advisory
  16. 2026-10-11 17:41 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-11 14:01 UTCEG score recompute
  18. 2026-10-11 14:01 UTCVendor advisory
  19. 2026-10-11 14:01 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-11 13:41 UTCEPSS rescoreEPSS 73% · 99th percentile
  21. 2026-10-11 10:24 UTCVendor advisory
  22. 2026-10-11 10:24 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-11 06:47 UTCVendor advisory
  24. 2026-10-11 06:47 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-11 03:10 UTCVendor advisory
Show 73 more
  1. 2026-10-11 03:10 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-10-10 23:29 UTCEG score recompute
  3. 2026-10-10 23:29 UTCVendor advisory
  4. 2026-10-10 23:29 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-10 19:55 UTCEPSS rescoreEPSS 73% · 99th percentile
  6. 2026-10-10 19:52 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-10 16:15 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-10 12:37 UTCVendor advisory
  9. 2026-10-10 12:37 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-10 09:00 UTCVendor advisory
  11. 2026-10-10 09:00 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-10 05:24 UTCVendor advisory
  13. 2026-10-10 05:23 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-10 01:47 UTCVendor advisory
  15. 2026-10-10 01:47 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-09 22:09 UTCVendor advisory
  17. 2026-10-09 22:09 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-09 18:32 UTCVendor advisory
  19. 2026-10-09 18:32 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-09 14:54 UTCVendor advisory
  21. 2026-10-09 14:54 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-09 11:15 UTCVendor advisory
  23. 2026-10-09 11:15 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-10-09 07:37 UTCVendor advisory
  25. 2026-10-09 07:36 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-10-09 04:00 UTCVendor advisory
  27. 2026-10-09 04:00 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  28. 2026-10-09 00:22 UTCVendor advisory
  29. 2026-10-09 00:22 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  30. 2026-10-08 20:45 UTCVendor advisory
  31. 2026-10-08 20:45 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  32. 2026-10-08 17:09 UTCVendor advisory
  33. 2026-10-08 17:09 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  34. 2026-10-08 13:31 UTCVendor advisory
  35. 2026-10-08 13:31 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  36. 2026-10-08 09:53 UTCVendor advisory
  37. 2026-10-08 09:53 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  38. 2026-10-08 06:16 UTCVendor advisory
  39. 2026-10-08 06:16 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  40. 2026-10-08 02:39 UTCEG score recompute
  41. 2026-10-08 02:39 UTCVendor advisory
  42. 2026-10-08 02:39 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  43. 2026-10-07 23:42 UTCEPSS rescoreEPSS 73% · 99th percentile
  44. 2026-10-07 23:03 UTCVendor advisory
  45. 2026-10-07 23:03 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-10-07 19:26 UTCVendor advisory
  47. 2026-10-07 19:26 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  48. 2026-10-07 15:49 UTCVendor advisory
  49. 2026-10-07 15:49 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  50. 2026-10-07 12:09 UTCVendor advisory
  51. 2026-10-07 12:08 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  52. 2026-10-07 08:31 UTCVendor advisory
  53. 2026-10-07 08:31 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  54. 2026-10-07 04:54 UTCVendor advisory
  55. 2026-10-07 04:54 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-10-07 01:17 UTCVendor advisory
  57. 2026-10-07 01:17 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-10-06 21:40 UTCVendor advisory
  59. 2026-10-06 21:40 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-10-06 18:03 UTCEG score recompute
  61. 2026-10-06 18:03 UTCVendor advisory
  62. 2026-10-06 18:03 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-10-06 15:12 UTCEPSS rescoreEPSS 73% · 99th percentile
  64. 2026-10-06 14:26 UTCVendor advisory
  65. 2026-10-06 14:26 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-10-06 10:49 UTCVendor advisory
  67. 2026-10-06 10:49 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  68. 2026-10-06 07:12 UTCVendor advisory
  69. 2026-10-06 07:12 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  70. 2026-10-06 03:35 UTCVendor advisory
  71. 2026-10-06 03:34 UTCVendor advisory
  72. 2026-10-06 03:34 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8
  73. 2026-10-06 03:34 UTCGHSA enrichmentGHSA-xg99-mpwj-gf2c · GitHub severity HIGH · GitHub CVSS 8.8

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCwhereisr0da/CVE-2018-8414-POC
    Published Aug 24, 2018

    Simple poc of CVE-2018-8414 Windows Package Setting RCE Vulnerability

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2018-8414?
CVE-2018-8414 is a critical-severity vulnerability; its CVE record was published on August 15, 2018. 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.
When was CVE-2018-8414 made public?
CVE-2018-8414 was made public on August 14, 2018: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 15, 2018. EchelonGraph's copy of the record carries a last-modified date of October 28, 2025; the record at its source may have been updated since.
Is CVE-2018-8414 actively exploited?
Yes. CISA added CVE-2018-8414 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2018-8414?
CVE-2018-8414 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2018-8414?
CVE-2018-8414 affects Microsoft Windows.
How do I remediate CVE-2018-8414?
A fix for CVE-2018-8414 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-8414 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-8414

Explore →

Is Your Infrastructure Affected by CVE-2018-8414?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs