Salt 3002 · Version Status
Salt 3002 End of Life Date
Salt 3002 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Salt 3002 is past end of life. This version no longer receives security patches. 1479 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 21, 2022
1479 days past EOL
Latest Release
3002.9
Standard release
Release Date
Oct 20, 2020
Salt 3002 series
| Version | Latest | EOL Date | Status |
|---|
| 2014.7 |
2014.7.9 |
May 31, 2016 |
EOL |
| 2015.5 |
2015.5.11 |
Nov 30, 2016 |
EOL |
| 2015.8 |
2015.8.13 |
Mar 31, 2017 |
EOL |
| 2016.3 |
2016.3.8 |
Nov 30, 2017 |
EOL |
| 2017.7 |
2017.7.8 |
Aug 30, 2019 |
EOL |
| 2018.3 |
2018.3.5 |
Oct 31, 2019 |
EOL |
| 2019.2 |
2019.2.8 |
Sep 30, 2020 |
EOL |
| 3000 |
3000.9 |
Aug 31, 2021 |
EOL |
What does Salt 3002 end of life mean?
When Salt 3002 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Salt 3002 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Salt 3006 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Salt 3002 reach end of life?
Salt 3002 reached end of life on April 21, 2022. This version is no longer receiving security patches.
Is Salt 3002 still supported?
No. Salt 3002 reached end of life on April 21, 2022 and is no longer receiving security patches.
What should I upgrade to from Salt 3002?
The recommended upgrade from Salt 3002 is
Salt 3006 — the latest actively supported version. Check the
Salt full timeline for all supported versions.
What are the security risks of running Salt 3002 past EOL?
When Salt 3002 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Salt should migrate immediately or implement compensating controls.