Salt's worker process vulnerable to denial of service through file read operation
Published 13 Jun 2025 · Updated 7 Jul 2026
Is your project on an affected salt?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=3007.0rc1 <3007.4
- Fixed in
- 3007.4
pip install 'salt>=3007.4'- Affected
- >=3006.0rc1 <3006.12
- Fixed in
- 3006.12
pip install 'salt>=3006.12'Details
Worker process denial of service through file read operation. .A vulnerability exists in the Master's “pub_ret” method which is exposed to all minions. The un-sanitized input value “jid” is used to construct a path which is then opened for reading. An attacker could exploit this vulnerabilities by attempting to read from a filename that will not return any data, e.g. by targeting a pipe node on the proc file system.
Is GHSA-989c-m532-p2hv in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected salt, and gives you the command that fixes it.
More advisories for salt
- HighCVE-2025-62348Salt junos Module Vulnerable to Code Injection via Specially Crafted YAML Payload · 30 Jan 2026
- HighCVE-2025-62349Salt Authentication Protocol Version Downgrade Allows Minion Impersonation · 30 Jan 2026
- CriticalCVE-2024-38824Salt vulnerable to directory traversal attack in file receiving method · 13 Jun 2025
- HighCVE-2025-22239Salt vulnerable to arbitrary event injection · 13 Jun 2025
- HighCVE-2025-22236Salt has minion event bus authorization bypass vulnerability · 13 Jun 2025
- MediumCVE-2024-38825Salt's salt.auth.pki module does not properly authenticate callers · 13 Jun 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.