SaltStack Salt Authentication Bypass by Capture-replay

Exploitation

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

CVSS

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

EPSS

• CVE-2022-22936: 0.83% estimated exploitation activity in the next 30 days; percentile 57.54 (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.

An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. Job publishes and file server replies are susceptible to replay attacks, which can result in an attacker replaying job publishes causing minions to run old jobs. File server replies can also be re-played. A sufficient craft attacker could gain root access on minion under certain scenarios.

Published by the source

30 Mar 2022, 00:00 UTC

Last modified by the source

22 Oct 2024, 15:01 UTC

Source last checked

26 Oct 2026, 13:22 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5r3f-3m3j-wcj2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5r3f-3m3j-wcj2

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

# Patch Next advisory brief: CVE-2022-22936

Advisory: SaltStack Salt Authentication Bypass by Capture-replay
IDs: CVE-2022-22936, GHSA-5r3f-3m3j-wcj2
Record: https://patchnext.com/advisories/cve-2022-22936 (revision 2, source checked 26 Oct 2026, 13:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: salt 3004.1, 3003.4, 3002.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI salt: affected < 3002.8; >= 3003, < 3003.4; >= 3004, < 3004.1; fixed in 3003.4, 3004.1, 3002.8

## 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-5r3f-3m3j-wcj2 (OSV record GHSA-5r3f-3m3j-wcj2 lists affected ranges: PyPI salt >=0 =3003 =3004 <3004.1 (fixed))
- Verified: https://github.com/advisories/GHSA-5r3f-3m3j-wcj2 (GitHub-reviewed advisory GHSA-5r3f-3m3j-wcj2 lists affected ranges: PyPI salt >=0 =3003 =3004 <3004.1)

Commands are suggestions: review each one before running it.