Saltstack's vulnerability profile centers on a single, narrowly scoped infrastructure-automation and configuration-management platform that has achieved prominence in enterprise deployment and cloud-native environments. Vulnerabilities affecting the vendor skew strongly toward critical-severity outcomes and frequently acquire public exploit code, reflecting both the deep system privileges that the automation layer commands and the appeal of the platform as a high-value target for post-compromise persistence and lateral movement. The exposure recurs persistently across Saltstack product versions through weakness classes including improper authentication, path-traversal conditions, sensitive-information exposure, and certificate-validation gaps—attack vectors that directly compromise the trust model underpinning remote agent communication and configuration dispatch. A moderate tendency toward confirmed in-the-wild exploitation adds urgency to patching; defenders should treat Saltstack disclosures as priority items for environments where the platform manages or touches critical infrastructure. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Saltstack over time
Signals from CVEs in this vendor scope (59 CVEs).
59 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-16846CRITICAL An issue was discovered in SaltStack Salt through 3002. Sending crafted web requests to the Salt API, with the SSH client enabled, can result in shell injection. | Nov 6, 2020 | 9.8 | 98 | YES | YES |
CVE-2020-11651CRITICAL An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class does not properly validate method calls. This allows a re | Apr 30, 2020 | 9.8 | 98 | YES | YES |
CVE-2020-11652MEDIUM 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 pa | Apr 30, 2020 | 6.5 | 96 | YES | YES |
CVE-2021-25282CRITICAL An issue was discovered in through SaltStack Salt before 3002.5. The salt.wheel.pillar_roots.write method is vulnerable to directory traversal. | Feb 27, 2021 | 9.1 | 86 | NO | YES |
CVE-2021-25281CRITICAL An issue was discovered in through SaltStack Salt before 3002.5. salt-api does not honor eauth credentials for the wheel_async client. Thus, an attacker can remotely run any wheel | Feb 27, 2021 | 9.8 | 86 | NO | YES |
CVE-2020-25592CRITICAL In SaltStack Salt through 3002, salt-netapi improperly validates eauth credentials and tokens. A user can bypass authentication and invoke Salt SSH. | Nov 6, 2020 | 9.8 | 73 | NO | YES |
CVE-2021-3197CRITICAL An issue was discovered in SaltStack Salt before 3002.5. The salt-api's ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options p | Feb 27, 2021 | 9.8 | 71 | NO | NO |
CVE-2019-17361CRITICAL In SaltStack Salt through 2019.2.0, the salt-api NET API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access | Jan 17, 2020 | 9.8 | 39 | NO | NO |
CVE-2021-25283CRITICAL An issue was discovered in through SaltStack Salt before 3002.5. The jinja renderer does not protect against server side template injection attacks. | Feb 27, 2021 | 9.8 | 35 | NO | NO |
CVE-2021-3148CRITICAL An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of differen | Feb 27, 2021 | 9.8 | 34 | NO | NO |
Signals from CVEs in this vendor scope (59 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Saltstack.
Media articles that mention a CVE ID that affects a product developed by Saltstack — matched by CVE ID, not by vendor name.