← console
voxell vciy

CVE-2025-22238: CVE-2025-22238 salt advisory

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: 3006.12; 3007.4 CVE record
  2. Later advisories still cover the fixes above and name higher ones: salt 3006.17 (CVE-2025-62348), 3007.9 (CVE-2025-62349) OSV advisories
  3. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  4. Check your version against the ranges this record publishes.

What it is stated by the CNA

Directory traversal attack in minion file cache creation. The master's default cache is vulnerable to a directory traversal attack. Which could be leveraged to write or overwrite 'cache' files outside of the cache directory.

weakness
Not named by the CNA. NVD maps it to CWE-22.
affected
VMware SALT
versions
No affected-version range in held sources.
fixed in
3006.12; 3007.4
fixed by package (from OSV advisories)
salt (PyPI): 3006.12; 3007.4 GHSA-r546-h3ff-q585 PYSEC-2026-1901
later fixes (from OSV advisories)
salt 3006.12 is inside a range CVE-2025-62348 (GHSA-77w2-v593-vxvv) lists as affected. That advisory is fixed in 3006.17.salt 3006.12 is inside a range CVE-2025-62349 (GHSA-vcf3-26xf-fw4m) lists as affected. That advisory is fixed in 3006.17.salt 3007.4 is inside a range CVE-2025-62349 (GHSA-vcf3-26xf-fw4m) lists as affected. That advisory is fixed in 3007.9.
severity
4.2 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N
assigned by
vmware
published
2025-06-13

check us docs.saltproject.io docs.saltproject.io

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
13 Jun 20250.00094
14 Jun 20250.00137
19 Jun 20250.00128
15 Jul 20250.00162
15 Jun 20260.00266scoring model v2026.06.15
3 Sep 20260.00266
8 Sep 20260.00288
14 Sep 20260.00289
17 Sep 20260.00291

21 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-09-17 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: 3006.12; 3007.4. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-22238', '2026-10-29T23:59:59.999999Z', now());