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."
CVE-2017-8464
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. 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)
- EPSS
- 99.8%
- KEV
- ⚠ Exploited
Published
June 15, 2017
Last Modified
April 22, 2026
Advisory Details (4)
Auto-updated May 2, 2026Microsoft Windows - '.LNK' Shortcut File Code Execution - Windows local Exploit
https://www.exploit-db.com/exploits/42429/Microsoft Windows - '.LNK' Shortcut File Code Execution (Metasploit) - Windows local Exploit
https://www.exploit-db.com/exploits/42382/Security 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-2017-8464All 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 128× in last 7d / 529× 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 709 total refreshes for this CVE.
- 2026-07-07 17:16 UTCCISA KEV update
- 2026-07-07 14:24 UTCEG score recompute
- 2026-07-07 14:24 UTCVendor advisory
- 2026-07-07 14:24 UTCGHSA enrichment
- 2026-07-07 10:16 UTCEG score recompute
- 2026-07-07 10:16 UTCVendor advisory
- 2026-07-07 10:16 UTCGHSA enrichment
- 2026-07-07 05:59 UTCEG score recompute
- 2026-07-07 05:59 UTCVendor advisory
- 2026-07-07 05:59 UTCGHSA enrichment
- 2026-07-07 01:52 UTCEG score recompute
- 2026-07-07 01:52 UTCVendor advisory
- 2026-07-07 01:52 UTCGHSA enrichment
- 2026-07-06 21:46 UTCEG score recompute
- 2026-07-06 21:46 UTCVendor advisory
- 2026-07-06 21:46 UTCGHSA enrichment
- 2026-07-06 17:39 UTCEG score recompute
- 2026-07-06 17:39 UTCVendor advisory
- 2026-07-06 17:38 UTCGHSA enrichment
- 2026-07-06 13:30 UTCEG score recompute
- 2026-07-06 13:30 UTCVendor advisory
- 2026-07-06 13:30 UTCGHSA enrichment
- 2026-07-06 09:23 UTCEG score recompute
- 2026-07-06 09:23 UTCVendor advisory
- 2026-07-06 09:22 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-06 05:15 UTCEG score recompute
- 2026-07-06 05:15 UTCVendor advisory
- 2026-07-06 05:15 UTCGHSA enrichment
- 2026-07-06 01:07 UTCEG score recompute
- 2026-07-06 01:07 UTCVendor advisory
- 2026-07-06 01:07 UTCGHSA enrichment
- 2026-07-05 21:01 UTCEG score recompute
- 2026-07-05 21:01 UTCVendor advisory
- 2026-07-05 21:01 UTCGHSA enrichment
- 2026-07-05 16:55 UTCEG score recompute
- 2026-07-05 16:55 UTCVendor advisory
- 2026-07-05 16:55 UTCGHSA enrichment
- 2026-07-05 12:49 UTCEG score recompute
- 2026-07-05 12:49 UTCVendor advisory
- 2026-07-05 12:48 UTCGHSA enrichment
- 2026-07-05 08:40 UTCEG score recompute
- 2026-07-05 08:40 UTCVendor advisory
- 2026-07-05 08:40 UTCGHSA enrichment
- 2026-07-05 04:34 UTCEG score recompute
- 2026-07-05 04:34 UTCVendor advisory
- 2026-07-05 04:33 UTCGHSA enrichment
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-05 00:27 UTCEG score recompute
- 2026-07-05 00:27 UTCVendor advisory
- 2026-07-05 00:27 UTCGHSA enrichment
- 2026-07-04 20:19 UTCEG score recompute
- 2026-07-04 20:19 UTCVendor advisory
- 2026-07-04 20:19 UTCGHSA enrichment
- 2026-07-04 16:12 UTCEG score recompute
- 2026-07-04 16:12 UTCVendor advisory
- 2026-07-04 16:12 UTCGHSA enrichment
- 2026-07-04 12:05 UTCEG score recompute
- 2026-07-04 12:05 UTCVendor advisory
- 2026-07-04 12:05 UTCGHSA enrichment
- 2026-07-04 07:58 UTCEG score recompute
- 2026-07-04 07:58 UTCVendor advisory
- 2026-07-04 07:58 UTCGHSA enrichment
- 2026-07-04 03:50 UTCEG score recompute
- 2026-07-04 03:50 UTCVendor advisory
- 2026-07-04 03:50 UTCGHSA enrichment
- 2026-07-03 23:42 UTCEG score recompute
- 2026-07-03 23:42 UTCVendor advisory
- 2026-07-03 23:42 UTCGHSA enrichment
- 2026-07-03 19:36 UTCEG score recompute
- 2026-07-03 19:36 UTCVendor advisory
- 2026-07-03 19:36 UTCGHSA enrichment
- 2026-07-03 15:30 UTCEG score recompute
- 2026-07-03 15:30 UTCVendor advisory
- 2026-07-03 15:30 UTCGHSA enrichment
- 2026-07-03 11:23 UTCEG score recompute
- 2026-07-03 11:23 UTCVendor advisory
- 2026-07-03 11:23 UTCGHSA enrichment
- 2026-07-03 07:17 UTCEG score recompute
- 2026-07-03 07:17 UTCVendor advisory
- 2026-07-03 07:17 UTCGHSA enrichment
- 2026-07-03 03:11 UTCEG score recompute
- 2026-07-03 03:11 UTCVendor advisory
- 2026-07-03 03:10 UTCGHSA enrichment
- 2026-07-02 23:04 UTCEG score recompute
- 2026-07-02 23:04 UTCVendor advisory
- 2026-07-02 23:04 UTCGHSA enrichment
- 2026-07-02 18:56 UTCEG score recompute
- 2026-07-02 18:56 UTCVendor advisory
- 2026-07-02 18:56 UTCGHSA enrichment
- 2026-07-02 14:50 UTCEG score recompute
- 2026-07-02 14:50 UTCVendor advisory
- 2026-07-02 14:49 UTCGHSA enrichment
- 2026-07-02 10:43 UTCEG score recompute
- 2026-07-02 10:43 UTCVendor advisory
- 2026-07-02 10:43 UTCGHSA enrichment
- 2026-07-02 06:33 UTCEG score recompute
- 2026-07-02 06:33 UTCVendor advisory
- 2026-07-02 06:33 UTCGHSA enrichment
- 2026-07-02 02:26 UTCEG score recompute
- 2026-07-02 02:26 UTCVendor advisory
Publicly available exploits
(7 references)Working exploit code is in the public domain (2 Metasploit modules) (3 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCTrG-1999/DetectPacket-CVE-2017-8464First seen Jun 8, 2022
Exploit vulnerabilities and vulnerability prevention implementation
Open source ↗ - GitHub PoCdoudouhala/CVE-2017-8464-exp-generatorFirst seen Aug 7, 2017
this tool can generate a exp for cve-2017-8486, it is developed by python
Open source ↗ - Exploit-DBEDB-42429First seen Aug 6, 2017
Microsoft Windows - '.LNK' Shortcut File Code Execution
Open source ↗ - GitHub PoC3gstudent/CVE-2017-8464-EXPFirst seen Aug 2, 2017
Support x86 and x64
Open source ↗ - Exploit-DBEDB-42382First seen Jul 26, 2017
Microsoft Windows - '.LNK' Shortcut File Code Execution (Metasploit)
Open source ↗ - Metasploitexploit/windows/local/cve_2017_8464_lnk_lpe✓ verifiedFirst seen Jun 13, 2017
LNK Code Execution Vulnerability
Open source ↗ - Metasploitexploit/windows/fileformat/cve_2017_8464_lnk_rce✓ verifiedFirst seen Jun 13, 2017
LNK Code Execution Vulnerability
Open source ↗
Frequently asked(6)
What is CVE-2017-8464?
When was CVE-2017-8464 disclosed?
Is CVE-2017-8464 actively exploited?
What is the CVSS score of CVE-2017-8464?
Which products are affected by CVE-2017-8464?
How do I remediate CVE-2017-8464?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-8464
Is Your Infrastructure Affected by CVE-2017-8464?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.