Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.2amended

Salt can cause Git Providers to get wrong data

CVE-2023-20898GHSA-qvh6-3j7x-3hq7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (salt 3006.2, 3005.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI salt

    Affected
    < 3005.2>= 3006.0rc1, < 3006.2
    Fixed in
    3005.2, 3006.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.2 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS
  • CVE-2023-20898: 0.32% estimated exploitation activity in the next 30 days; percentile 24.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Git Providers can read from the wrong environment because they get the same cache directory base name in Salt masters prior to 3005.2 or 3006.2. Anything that uses Git Providers with different environments can get garbage data or the wrong data, which can lead to wrongful data disclosure, wrongful executions, data corruption and/or crash.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-qvh6-3j7x-3hq7

  2. Revision 1 · created ·

    Published from osv record GHSA-qvh6-3j7x-3hq7

Agent brief

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

# Patch Next advisory brief: CVE-2023-20898

Advisory: Salt can cause Git Providers to get wrong data
IDs: CVE-2023-20898, GHSA-qvh6-3j7x-3hq7
Record: https://patchnext.com/advisories/cve-2023-20898 (revision 2, source checked 26 Oct 2026, 13:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: salt 3006.2, 3005.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI salt: affected < 3005.2; >= 3006.0rc1, < 3006.2; fixed in 3005.2, 3006.2

## 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-qvh6-3j7x-3hq7 (OSV record GHSA-qvh6-3j7x-3hq7 lists affected ranges: PyPI salt >=0 =3006.0rc1 <3006.2 (fixed))
- Verified: https://github.com/advisories/GHSA-qvh6-3j7x-3hq7 (GitHub-reviewed advisory GHSA-qvh6-3j7x-3hq7 lists affected ranges: PyPI salt >=0 =3006.0rc1 <3006.2)

Commands are suggestions: review each one before running it.

Loading voting…