CVE-2024-38825: CVE-2024-38825 Salt Advisory
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
- Upgrade to the fixed version for your release line, or later: 3006.12; 3007.4 CVE record
- Later advisories still cover the fixes above and name higher ones: salt 3006.17 (CVE-2025-62348), 3007.9 (CVE-2025-62349) OSV advisories
- 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
- Check your version against the ranges this record publishes.
What it is stated by the CNA
The salt.auth.pki module does not properly authenticate callers. The "password" field contains a public certificate which is validated against a CA certificate by the module. This is not pki authentication, as the caller does not need access to the corresponding private key for the authentication attempt to be accepted.
- weakness
- Not named by the CNA. NVD maps it to CWE-287.
- 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-4j59-vv55-q6h3 PYSEC-2026-1893
- 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
- 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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
| date | EPSS | event |
|---|---|---|
| 13 Jun 2025 | 0.00025 | |
| 14 Jun 2025 | 0.00026 | |
| 8 Jul 2025 | 0.00035 | |
| 15 Jul 2025 | 0.00043 | |
| 15 Jun 2026 | 0.00129 | scoring model v2026.06.15 |
| 1 Aug 2026 | 0.00139 | |
| 3 Sep 2026 | 0.00147 | |
| 14 Sep 2026 | 0.00152 | |
| 17 Sep 2026 | 0.00154 |
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.
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.
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-2024-38825', '2026-10-31T23:59:59.999999Z', now());