CVE-2017-8464

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-02-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2017-17414 (ENISA EUVD) · GHSA-v5x6-r6hp-xgpc (GitHub Security Advisories)Source: ENISA EUVD

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: 90%CVSS: 8.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

Windows Shell in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows local users or remote attackers to execute arbitrary code via a crafted .LNK file, which is not properly handled during icon display in Windows Explorer or any other application that parses the icon of the shortcut. aka "LNK Remote Code Execution Vulnerability."

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

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
90%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.8 HIGH.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
90% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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-2017-8464

Published

June 15, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Nov 16, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: microsoft.
Web page

Microsoft Windows - '.LNK' Shortcut File Code Execution - Windows local Exploit

https://www.exploit-db.com/exploits/42429/
Web page

Microsoft Windows - '.LNK' Shortcut File Code Execution (Metasploit) - Windows local Exploit

https://www.exploit-db.com/exploits/42382/
Microsoft

Security Update Guide - Microsoft Security Response Center

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

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/98818

Vendor Advisories for CVE-2017-8464(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 61× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 1,759 rows 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. None are among the latest 100 rows. The 1,659 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (2 Metasploit modules, 2 Exploit-DB entries, 3 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Metasploitexploit/windows/local/cve_2017_8464_lnk_lpe✓ verified
    Published Dec 8, 2017

    LNK Code Execution Vulnerability

    Open source ↗
  • Metasploitexploit/windows/fileformat/cve_2017_8464_lnk_rce✓ verified
    Published Aug 3, 2017

    LNK Code Execution Vulnerability

    Open source ↗
  • GitHub PoCTrG-1999/DetectPacket-CVE-2017-8464
    Published Jun 8, 2022

    Exploit vulnerabilities and vulnerability prevention implementation

    Open source ↗
  • GitHub PoCdoudouhala/CVE-2017-8464-exp-generator
    Published Aug 7, 2017

    this tool can generate a exp for cve-2017-8486, it is developed by python

    Open source ↗
  • Exploit-DBEDB-42429
    Published Aug 6, 2017

    Microsoft Windows - '.LNK' Shortcut File Code Execution

    Open source ↗
  • GitHub PoC3gstudent/CVE-2017-8464-EXP
    Published Aug 2, 2017

    Support x86 and x64

    Open source ↗
  • Exploit-DBEDB-42382
    Published Jul 26, 2017

    Microsoft Windows - '.LNK' Shortcut File Code Execution (Metasploit)

    Open source ↗

Frequently asked(6)

What is CVE-2017-8464?
CVE-2017-8464 is a critical-severity vulnerability; its CVE record was published on June 15, 2017. Windows Shell in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows local users or remote attackers to execute arbitrary code via a crafted .LNK file,…
When was CVE-2017-8464 made public?
CVE-2017-8464 was made public on June 13, 2017: 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 June 15, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-8464 actively exploited?
Yes. CISA added CVE-2017-8464 to the Known Exploited Vulnerabilities catalog on February 10, 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-2017-8464?
CVE-2017-8464 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-2017-8464?
CVE-2017-8464 affects Microsoft Windows.
How do I remediate CVE-2017-8464?
A fix for CVE-2017-8464 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-8464 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-8464

Explore →

Is Your Infrastructure Affected by CVE-2017-8464?

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