Salt End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Salt versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2014.7 | 2014.7.9 | Jul 15, 2014 | May 31, 2016 | 3675 days past EOL | EOL |
| 2015.5 | 2015.5.11 | May 6, 2015 | Nov 30, 2016 | 3492 days past EOL | EOL |
| 2015.8 | 2015.8.13 | Jul 2, 2015 | Mar 31, 2017 | 3371 days past EOL | EOL |
| 2016.3 | 2016.3.8 | Feb 2, 2016 | Nov 30, 2017 | 3127 days past EOL | EOL |
| 2017.7 | 2017.7.8 | Jun 14, 2017 | Aug 30, 2019 | 2489 days past EOL | EOL |
| 2018.3 | 2018.3.5 | Feb 22, 2018 | Oct 31, 2019 | 2427 days past EOL | EOL |
| 2019.2 | 2019.2.8 | Jan 7, 2019 | Sep 30, 2020 | 2092 days past EOL | EOL |
| 3000 | 3000.9 | Feb 1, 2020 | Aug 31, 2021 | 1757 days past EOL | EOL |
| 3001 | 3001.8 | Jun 9, 2020 | Dec 31, 2021 | 1635 days past EOL | EOL |
| 3002 | 3002.9 | Oct 20, 2020 | Apr 21, 2022 | 1524 days past EOL | EOL |
| 3003 | 3003.5 | Mar 23, 2021 | Sep 30, 2022 | 1362 days past EOL | EOL |
| 3004 | 3004.2 | Oct 12, 2021 | Apr 18, 2023 | 1162 days past EOL | EOL |
| 3005 | 3005.5 | Aug 22, 2022 | Feb 25, 2024 | 849 days past EOL | EOL |
| 3006 LTS | 3006.25 | Apr 18, 2023 | Jun 30, 2027 | 372 days remaining | Active |
| 3007 | 3007.14 | Mar 6, 2024 | Jul 31, 2026 | 38 days remaining | Warning |
| 3008 LTS | 3008.1 | May 27, 2026 | Jun 30, 2028 | 738 days remaining | Active |
What does Salt end of life mean for your organization?
When a version of Salt reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Salt should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Salt versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →