NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2019-17361 — salt

CRITICAL

CVE-2019-17361 is a critical-severity (CVSS 9.8) CWE-77 vulnerability in salt. EPSS puts its 30-day exploitation probability at 15.1% (97th percentile). A fix is available for salt — see the affected versions and patch details below.

SaltStack Salt is vulnerable to command injection

Also known asGHSA-q53j-p6r2-g2v4PYSEC-2020-177
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
15.1%probability of exploitation in next 30 days
Moderate Risk-0.05%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
12.9%16.8%20.6%24.5%22.3%15.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍salt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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 to the API endpoint to execute arbitrary code on the salt-api host.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIsaltall versions2019.2.3pip install --upgrade 'salt==2019.2.3'

Affected Products

4 products · 6 configurations
OS
ubuntu linuxcanonical
2 versions
16.0418.04
OS
debian linuxdebian
2 versions
9.010.0
OS
leapopensuse
1 version
15.1
Application
saltsaltstack
≤ 2019.2.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for salt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update salt to 2019.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17361 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

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 to the API endpoint to execute arbitrary code on the salt-api host.
O3 Security · Impact-Aware SCA

Is CVE-2019-17361 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-17361: salt RCE — Fixed in 2019.2.3