Skip to content
Fencer Vulns
high 8.8

CVE-2020-1421 in the critical feed json

A remote code execution vulnerability exists in Microsoft Windows that could allow remote code execution if a .LNK file is processed.An att…

published 2020-07-14 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-12297

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
74.5%
EPSS 74.5% chance of exploitation in 30 days, percentile 99.4%
public exploits
0
none known

Summary

A remote code execution vulnerability exists in Microsoft Windows that could allow remote code execution if a .LNK file is processed.An attacker who successfully exploited this vulnerability could gain the same user rights as the local user, aka 'LNK Remote Code Execution Vulnerability'.

Patch / fix

Exploit prediction

74.50% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Windows 10 Version 2004 for 32-bit Systems
  • Microsoft Windows 10 Version 2004 for ARM64-based Systems
  • Microsoft Windows 10 Version 2004 for x64-based Systems
  • Microsoft Windows Server, version 2004 (Server Core installation)
  • Microsoft Windows
  • Microsoft Windows Server
  • Microsoft Windows 10 Version 1909 for 32-bit Systems
  • Microsoft Windows 10 Version 1909 for x64-based Systems
  • Microsoft Windows 10 Version 1909 for ARM64-based Systems
  • Microsoft Windows Server, version 1909 (Server Core installation)
  • Microsoft Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Windows 10 Version 1903 for x64-based Systems
  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft Windows Server, version 1903 (Server Core installation)

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.