Salt's worker process vulnerable to denial of service through file read operation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.6 · CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:H

EPSS

• CVE-2025-22242: 0.14% estimated exploitation activity in the next 30 days; percentile 3.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Worker process denial of service through file read operation. .A vulnerability exists in the Master's “pubret” 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.

Published by the source

13 Jun 2025, 09:30 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:32 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-989c-m532-p2hv

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-989c-m532-p2hv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-22242

Advisory: Salt's worker process vulnerable to denial of service through file read operation
IDs: CVE-2025-22242, GHSA-989c-m532-p2hv
Record: https://patchnext.com/advisories/cve-2025-22242 (revision 2, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: salt 3007.4, 3006.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI salt: affected >= 3007.0rc1, < 3007.4; >= 3006.0rc1, < 3006.12; fixed in 3007.4, 3006.12

## Suggested inspection (read-only)
- `python -m pip show salt`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on salt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-989c-m532-p2hv (OSV record GHSA-989c-m532-p2hv lists affected ranges: PyPI salt >=3007.0rc1 =3006.0rc1 <3006.12 (fixed))
- Verified: https://github.com/advisories/GHSA-989c-m532-p2hv (GitHub-reviewed advisory GHSA-989c-m532-p2hv lists affected ranges: PyPI salt >=3007.0rc1 =3006.0rc1 <3006.12)

Commands are suggestions: review each one before running it.