Salt · Lifecycle Status

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.

Salt 3007 reaches end of life on July 31, 2026. Plan your migration now — 83 days remaining.
Latest Active
3006.24
3006 series
Next EOL
3007
Jul 31, 2026
Active Versions
1
of 15 total
EOL Versions
13
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20152016201720182019202020212022202320242025202620272014.72015.52015.82016.32017.72018.32019.230003001300230033004300530063007TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2014.7 2014.7.9 Jul 15, 2014 May 31, 2016 3630 days past EOL EOL
2015.5 2015.5.11 May 6, 2015 Nov 30, 2016 3447 days past EOL EOL
2015.8 2015.8.13 Jul 2, 2015 Mar 31, 2017 3326 days past EOL EOL
2016.3 2016.3.8 Feb 2, 2016 Nov 30, 2017 3082 days past EOL EOL
2017.7 2017.7.8 Jun 14, 2017 Aug 30, 2019 2444 days past EOL EOL
2018.3 2018.3.5 Feb 22, 2018 Oct 31, 2019 2382 days past EOL EOL
2019.2 2019.2.8 Jan 7, 2019 Sep 30, 2020 2047 days past EOL EOL
3000 3000.9 Feb 1, 2020 Aug 31, 2021 1712 days past EOL EOL
3001 3001.8 Jun 9, 2020 Dec 31, 2021 1590 days past EOL EOL
3002 3002.9 Oct 20, 2020 Apr 21, 2022 1479 days past EOL EOL
3003 3003.5 Mar 23, 2021 Sep 30, 2022 1317 days past EOL EOL
3004 3004.2 Oct 12, 2021 Apr 18, 2023 1117 days past EOL EOL
3005 3005.5 Aug 22, 2022 Feb 25, 2024 804 days past EOL EOL
3006 LTS 3006.24 Apr 18, 2023 Jul 31, 2027 448 days remaining Active
3007 3007.14 Mar 6, 2024 Jul 31, 2026 83 days remaining Warning

What does Salt end of life mean for your organization?

When a Salt version 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Salt?
The next Salt version reaching EOL is 3007 on July 31, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Salt?
The latest active version of Salt is 3006.24. Always verify against the table above as support windows can change.
What happens when Salt reaches end of life?
When Salt reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Salt?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Salt versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →