Salt End of Life Dates
other
Developers rely on accurate and timely information to manage their infrastructure effectively, and this is particularly important when it comes to tracking end-of-life dates for critical tools like Salt. Created to simplify infrastructure management, Salt has been maintained by its community since its inception, providing a robust framework for automating and securing complex systems. The need for a reliable tracking system arose from the complexity of managing multiple versions and ensuring seamless upgrades, which is why a dedicated platform for monitoring Salt's lifecycle has become essential for teams that depend on this tool.
The landscape of Salt's versions is characterized by a total of 16 releases, with 13 of them having already reached their end-of-life. Currently, only 3 versions remain active and supported, with the latest stable version being 3006.25. Looking ahead, the next significant milestone is the end-of-life date for version 3007, slated for July 31, 2026. This follows the last end-of-life date, which occurred on February 25, 2024, for version 3005. Keeping track of these timelines is crucial for planning upgrades and ensuring that systems remain secure and compliant.
Given the current security landscape, it's notable that Salt has not been associated with any tracked CVEs, resulting in zero critical vulnerabilities. Without a most affected version due to the absence of CVEs, the focus for developers should be on maintaining awareness of the upcoming end-of-life dates and planning their system updates accordingly. Since there are no known vulnerabilities, the priority is on timely upgrades to newer, supported versions, ensuring that systems continue to receive necessary security patches and updates, thereby minimizing potential risks associated with using outdated software.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 3008 LTS | May 27, 2026 | Jun 30, 2027 | Jun 30, 2028 | in 707d | 3008.2 | — | Active | |
| 3007 | Mar 6, 2024 | Jun 30, 2026 | Jul 31, 2026 | in 7d | 3007.14 | — | EOL soon | |
| 3006 LTS | Apr 18, 2023 | Jul 31, 2026 | Jun 30, 2027 | in 341d | 3006.27 | — | Active | |
| 3005 | Aug 22, 2022 | Aug 25, 2023 | Feb 25, 2024 | 880d ago | 3005.5 | — | EOL | |
| 3004 | Oct 12, 2021 | Oct 18, 2022 | Apr 18, 2023 | 1193d ago | 3004.2 | — | EOL | |
| 3003 | Mar 23, 2021 | Mar 31, 2022 | Sep 30, 2022 | 1393d ago | 3003.5 | — | EOL | |
| 3002 | Oct 20, 2020 | Oct 21, 2021 | Apr 21, 2022 | 1555d ago | 3002.9 | — | EOL | |
| 3001 | Jun 9, 2020 | Jun 30, 2021 | Dec 31, 2021 | 1666d ago | 3001.8 | — | EOL | |
| 3000 | Feb 1, 2020 | Feb 28, 2021 | Aug 31, 2021 | 1788d ago | 3000.9 | — | EOL | |
| 2019.2 | Jan 7, 2019 | Mar 31, 2020 | Sep 30, 2020 | 2123d ago | 2019.2.8 | — | EOL | |
| 2018.3 | Feb 22, 2018 | Apr 30, 2019 | Oct 31, 2019 | 2458d ago | 2018.3.5 | — | EOL | |
| 2017.7 | Jun 14, 2017 | Jun 30, 2018 | Aug 30, 2019 | 2520d ago | 2017.7.8 | — | EOL | |
| 2016.3 | Feb 2, 2016 | May 31, 2017 | Nov 30, 2017 | 3158d ago | 2016.3.8 | — | EOL | |
| 2015.8 | Jul 2, 2015 | Sep 30, 2016 | Mar 31, 2017 | 3402d ago | 2015.8.13 | — | EOL | |
| 2015.5 | May 6, 2015 | May 31, 2016 | Nov 30, 2016 | 3523d ago | 2015.5.11 | — | EOL | |
| 2014.7 | Jul 15, 2014 | Nov 30, 2015 | May 31, 2016 | 3706d ago | 2014.7.9 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
