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

CVE-2018-15751 — salt

CRITICAL

CVE-2018-15751 is a critical-severity (CVSS 9.8) Improper Authentication vulnerability in salt. A fix is available for salt — see the affected versions and patch details below.

SaltStack Salt Remote command execution and incorrect access control when using salt-api

Also known asGHSA-x549-r7m8-gv63PYSEC-2018-30
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.9%probability of exploitation in next 30 days
Lower Risk-0.34%
Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk
0.00%2.22%4.43%6.65%0.7%4.9%Apr 26Aug 26Oct 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

3 pkgs affected
🐍salt🐍salt🐍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

SaltStack Salt 2016.11.x before 2016.11.10, 2017.7.x before 2017.7.8 and 2018.3.x before 2018.3.3 allow remote attackers to bypass authentication and execute arbitrary commands via salt-api(netapi).

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIsalt≥ 2017.7.0&&< 2017.7.82017.7.8pip install --upgrade 'salt==2017.7.8'
🐍PyPIsalt≥ 2018.3.0&&< 2018.3.32018.3.3pip install --upgrade 'salt==2018.3.3'
🐍PyPIsalt≥ 2016.11.0&&< 2016.11.102016.11.10pip install --upgrade 'salt==2016.11.10'

Affected Products

1 product · 2 configurations
Application
saltsaltstack
≥ 2018.3.0 && < 2018.3.3
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 2017.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-15751 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

UbuntuCRITICAL
USN-4459-1UbuntuUSN-4769-1Ubuntu

Frequently Asked Questions

SaltStack Salt 2016.11.x before 2016.11.10, 2017.7.x before 2017.7.8 and 2018.3.x before 2018.3.3 allow remote attackers to bypass authentication and execute arbitrary commands via salt-api(netapi).
O3 Security · Impact-Aware SCA

Is CVE-2018-15751 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2018-15751: salt — Fixed in 2017.7.8