Skip to content
Fencer Intel
high 8.8

CVE-2020-1286 in the critical feed json

A remote code execution vulnerability exists when the Windows Shell does not properly validate file paths.An attacker who successfully expl…

published 6y ago modified 4mo ago also EUVD-2020-12165

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

Summary

A remote code execution vulnerability exists when the Windows Shell does not properly validate file paths.An attacker who successfully exploited this vulnerability could run arbitrary code in the context of the current user, aka 'Windows Shell Remote Code Execution Vulnerability'.

Patch / fix

Is CVE-2020-1286 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

12.07% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

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
  • 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)
  • Microsoft Windows 10 Version 2004 for x64-based Systems
  • Microsoft Windows 10 Version 2004 for ARM64-based Systems
  • Microsoft Windows Server, version 2004 (Server Core installation)

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel 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.