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

SaltStack Salt Directory traversal vulnerability in minion id validationGHSA-j6gj-pg62-x8j6

CRITICALFix: saltstack/salt@80d9030

GHSA-j6gj-pg62-x8j6 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in salt. A fix is available for salt — see the affected versions and patch details below.

Also known asCVE-2017-14695PYSEC-2017-36
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk
0.00%1.35%2.70%4.05%0.3%3.2%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

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

Directory traversal vulnerability in minion id validation in SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x before 2017.7.2 allows remote minions with incorrect credentials to authenticate to a master via a crafted minion ID. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12791.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIsaltall versions2016.3.8pip install --upgrade 'salt==2016.3.8'
🐍PyPIsalt≥ 2016.11.0&&< 2016.11.82016.11.8pip install --upgrade 'salt==2016.11.8'
🐍PyPIsalt≥ 2017.7.0&&< 2017.7.22017.7.2pip install --upgrade 'salt==2017.7.2'

Affected Products

1 product · 15 configurations
Application
saltsaltstack
≤ 2016.3.7
11 versions
2016.112016.11.02016.11.12016.11.22016.11.32016.11.42016.11.52016.11.62016.11.72017.7.02017.7.1

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 2016.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j6gj-pg62-x8j6 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Directory traversal vulnerability in minion id validation in SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x before 2017.7.2 allows remote minions with incorrect credentials to authenticate to a master via a crafted minion ID. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12791.
O3 Security · Impact-Aware SCA

Is GHSA-j6gj-pg62-x8j6 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
SaltStack Salt Directory traversal vulnerability in minion id…