CVE-2017-8464

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Microsoft Windows. For every flaw being used in attacks, see Exploited flaws; for Microsoft’s, see Microsoft flaws being used in attacks.

CVE-2017-8464 is a security flaw in Microsoft Windows, Microsoft’s operating system for PCs and servers. Someone who already has a way in can use Microsoft Windows to run their own code. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 10 Feb 2022.[1]

Microsoft Windows is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Microsoft has published a fix or advice.

Description

CISA calls it a shell (.lnk) remote code execution in Microsoft Windows. In its words: “Windows Shell in multiple versions of Microsoft Windows allows local users or remote attackers to execute arbitrary code via a crafted .LNK file”[1]

The CVE record adds: “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."”[2]

It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Microsoft’s advisory has them[3]. CISA names the product as Microsoft Windows.

Every device with Microsoft Windows needs the update.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 10 Feb 2022, 1,701 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 10 Aug 2022 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 90%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Microsoft has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Update Microsoft Windows now.On Windows: Settings, Windows Update, Check for updates, then restart. Office updates come the same way, or from any Office app: File, Account, Update Options. Then turn on automatic updates, so the next fix arrives on its own.
  2. If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 90%.[4]

See also

Other Microsoft Windows flaws

Similar flaws

  • CVE-2026-111357, Ivanti Connect Secure: missing authentication for critical function ·
  • CVE-2026-97229, GitLab Community Edition and Enterprise Edition: integer overflow or wraparound ·
  • CVE-2026-76418, Cisco Secure Firewall ASA Software and Cisco Secure FTD Software: unchecked return value to NULL pointer dereference ·
  • CVE-2026-48356, Adobe Commerce and Magento: unrestricted upload of file with dangerous type ·
  • CVE-2026-111497, Google Brotli: unchecked return value ·

Added the same day

  • CVE-2021-36934, Microsoft Windows: SAM local privilege escalation ·
  • CVE-2020-0796, Microsoft SMBv3: remote code execution ·
  • CVE-2018-1000861, Jenkins Stapler Web Framework: stapler web framework deserialization of untrusted data ·
  • CVE-2017-9791, Apache Struts 1: improper input validation ·
  • CVE-2017-10271, Oracle WebLogic Server: corporation webLogic server remote code execution ·

Every Microsoft flaw on CISA’s list · Everything added in February 2022

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Microsoft Windows Shell (.lnk) Remote Code Execution Vulnerability”. Known Exploited Vulnerabilities Catalog, added 10 Feb 2022.
  2. ^ National Institute of Standards and Technology. “CVE-2017-8464 Detail”. National Vulnerability Database, published 15 Jun 2017.
  3. ^ Microsoft. Advisories and fixes: portal.msrc.microsoft.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.900, percentile 99.8, 31 Oct 2026.
  5. CVE Program. “CVE-2017-8464”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.