CVE-2020-11652

CRITICALNVD 6.59.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 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 6.5 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 6.5 MEDIUM 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-2020-0172 (ENISA EUVD) · GHSA-vp49-2g4r-m3x3 (GitHub Security Advisories) · PYSEC-2020-103 (OSV.dev)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 every mission impact level
CISA-KEV: ExploitedEPSS PROB: 86%CVSS: 6.5Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class allows access to some methods that improperly sanitize paths. These methods allow arbitrary directory access to authenticated users.

CVSS v3
6.5
EG Score
9.0CRITICALhigh confidence
EG Risk
69
EG Risk 69/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 or medium mission impact and sooner than that at high.
EPSS PROB
86%
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 6.5 MEDIUM.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
86% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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 Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days 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 or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)14 days 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 partial (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-2020-11652

Published

April 30, 2020

Last Modified

November 7, 2025

Advisory Details (7)

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

SaltStack FrameWork Vulnerabilities Affecting Cisco Products

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-salt-2vx545AG
Web pageMentions a patch (unverified)

[SECURITY] [DLA 2223-1] salt security update

https://lists.debian.org/debian-lts-announce/2020/05/msg00027.html
Web page

salt/doc/topics/releases/3000.2.rst at v3000.2_docs · saltstack/salt · GitHub

https://github.com/saltstack/salt/blob/v3000.2_docs/doc/topics/releases/3000.2.rst
Web page

Support Content Notification - Support Portal - Broadcom support portal

http://www.vmware.com/security/advisories/VMSA-2020-0009.html

Vendor Advisories for CVE-2020-11652(1)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntusalt-syndic (2015.8.8+ds-1ubuntu0.1) @ xenial2026-11-12ubuntu
ubuntusalt-syndic (0.17.5+ds-1ubuntu0.1~esm2) @ trusty2026-11-12ubuntu
pipsalt @ 2019.2.4 (fixes < 2019.2.4)—ghsa
pipsalt @ 3000.2 (fixes >= 3000, < 3000.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(19 across 19 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 2019.2.4-r0: fixed in 2019.2.4-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 2019.2.4-r0: fixed in 2019.2.4-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
salt—
  • 3000 up to 3000.2-r0: fixed in 3000.2-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
salt2018.3.4+dfsg1-6
  • every version up to 2018.3.4+dfsg1-6+deb10u1: fixed in 2018.3.4+dfsg1-6+deb10u1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
salt2014.1.13+ds-3
  • every version up to 2014.1.13+ds-3+deb8u1: fixed in 2014.1.13+ds-3+deb8u1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
salt2016.11.2+ds-1, 2016.11.2+ds-1+deb9u1, 2016.11.2+ds-1+deb9u2, 2016.11.2+ds-1+deb9u3
  • every version up to 2016.11.2+ds-1+deb9u3: fixed in 2016.11.2+ds-1+deb9u3
  • every version up to 2016.11.2+ds-1+deb9u4: fixed in 2016.11.2+ds-1+deb9u4
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
salt0.10.0 ... 3000.1 (160 versions)
  • every version up to 2019.2.4: fixed in 2019.2.4
  • 3000 up to 3000.2: fixed in 3000.2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

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 13× in last 7d / 47× 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 808 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 708 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(5 references)

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

  • Metasploitauxiliary/gather/saltstack_salt_root_key✓ verified
    Published May 12, 2020

    SaltStack Salt Master Server Root Key Disclosure

    Open source ↗
  • Metasploitexploit/linux/misc/saltstack_salt_unauth_rce✓ verified
    Published May 12, 2020

    SaltStack Salt Master/Minion Unauthenticated RCE

    Open source ↗
  • GitHub PoClimon768/CVE-2020-11652-POC
    Published Jan 17, 2024

    This is a fix POC CVE-2020-11651 & CVE-2020-11651

    Open source ↗
  • GitHub PoCAl1ex/CVE-2020-11652
    Published Dec 25, 2020

    CVE-2020-11652 & CVE-2020-11651

    Open source ↗
  • Exploit-DBEDB-48421
    Published May 5, 2020

    Saltstack 3000.1 - Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2020-11652?
CVE-2020-11652 is a critical-severity vulnerability; its CVE record was published on April 30, 2020. An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class allows access to some methods that improperly sanitize paths. These methods allow arbitrary directory access to authenticated users.
When was the CVE record for CVE-2020-11652 published?
The CVE record for CVE-2020-11652 was published on April 30, 2020. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 7, 2025; the record at its source may have been updated since.
Is CVE-2020-11652 actively exploited?
Yes. CISA added CVE-2020-11652 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting SaltStack Salt. 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-2020-11652?
CVE-2020-11652 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2020-11652?
CVE-2020-11652 affects SaltStack Salt. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2020-11652?
A fix for CVE-2020-11652 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-11652 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-11652

Explore →

Is Your Infrastructure Affected by CVE-2020-11652?

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