Salt End of Life (EOL) Dates and End of Support (EOS) Dates
Salt end of life (EOL) and end of support (EOS) dates: 14 Salt versions have reached EOL, including Salt 3007 (EOL date: Jul 31, 2026) — no longer receiving security updates or patches. Salt 3008.5 LTS is the current supported release, with support through Jun 30, 2028 — 2 versions in active support. Also see Ansible EOSL dates for related end-of-life information.
Currently Supported Salt Releases - Active EOS/EOSL Support (2)
Salt End of Life (EOL) Releases - No Longer Supported (14)
| Release | Released | CVE & Critical Support | Active Support | Latest | LTS |
|---|---|---|---|---|---|
| 3007 | (2 years and 8 months ago) | (3 months ago) | (4 months ago) | 3007.17 (3 weeks and 5 days ago) | - |
| 3005 | (4 years and 3 months ago) | (2 years and 8 months ago) | (3 years and 2 months ago) | 3005.5 (2 years and 9 months ago) | - |
| 3004 | (5 years and 1 month ago) | (3 years and 7 months ago) | (4 years and 1 month ago) | 3004.2 (4 years and 6 months ago) | - |
| 3003 | (5 years and 7 months ago) | (4 years and 1 month ago) | (4 years and 7 months ago) | 3003.5 (4 years and 5 months ago) | - |
| 3002 | (6 years and 1 month ago) | (4 years and 7 months ago) | (5 years and 1 month ago) | 3002.9 (4 years and 5 months ago) | - |
| 3001 | (6 years and 5 months ago) | (4 years and 10 months ago) | (5 years and 4 months ago) | 3001.8 (5 years and 2 months ago) | - |
| 3000 | (6 years and 9 months ago) | (5 years and 2 months ago) | (5 years and 8 months ago) | 3000.9 (5 years and 8 months ago) | - |
| 2019.2 | (7 years and 10 months ago) | (6 years and 1 month ago) | (6 years and 7 months ago) | 2019.2.8 (5 years and 11 months ago) | - |
| 2018.3 | (8 years and 9 months ago) | (7 years ago) | (7 years and 6 months ago) | 2018.3.5 (6 years and 10 months ago) | - |
| 2017.7 | (9 years and 5 months ago) | (7 years and 2 months ago) | (8 years and 4 months ago) | 2017.7.8 (8 years and 2 months ago) | - |
| 2016.3 | (10 years and 9 months ago) | (8 years and 11 months ago) | (9 years and 5 months ago) | 2016.3.8 (9 years and 2 months ago) | - |
| 2015.8 | (11 years and 4 months ago) | (9 years and 7 months ago) | (10 years and 1 month ago) | 2015.8.13 (9 years and 10 months ago) | - |
| 2015.5 | (11 years and 6 months ago) | (9 years and 11 months ago) | (10 years and 5 months ago) | 2015.5.11 (10 years and 4 months ago) | - |
| 2014.7 | (12 years and 4 months ago) | (10 years and 5 months ago) | (10 years and 11 months ago) | 2014.7.9 (10 years and 8 months ago) | - |
Running an unsupported Salt release leaves your infrastructure exposed, so the Salt end of life dates are worth knowing before they pass. The Salt Project software for configuration automation ships a long-term LTS line and a short-term STS line, and each one stops receiving security patches on a different day. This guide shows which release is safe to run today.
Salt End of Life Dates and Version Support Lifecycle
The Salt version support lifecycle sets how long each release gets official packages, testing and technical support. As of October 2026, Salt 3008 is the only release with full support, Salt 3006 gets security fixes only, and Salt 3007 has no maintenance left.
| Release | Type | Release date | Active support through | CVE and critical support through |
|---|---|---|---|---|
| 3008 | LTS | May 27, 2026 | June 2027 | June 2028 |
| 3007 | STS | March 6, 2024 | June 2026 | None |
| 3006 | LTS | April 18, 2023 | July 2026 | June 2027 |
These dates come from the Salt Project documentation and hold as of October 27, 2026.
3008 LTS and 3006 LTS: Where Each LTS Stands
3008 LTS, released May 27, 2026, is the current LTS and the latest release to run. It gets active updates until June 2027, then CVE fixes until June 2028. Maintainers confirmed on GitHub that 3006 moved into security maintenance for a year, with a few extra bugfix builds promised while teams upgrade, so 3006 remains a supported release for CVE fixes only. Because the policy is one LTS a year, the next LTS should arrive in 2027.
3007 STS: Now an Unsupported Release
3007 STS reached the end of its life when active support stopped in June 2026, and the table lists no CVE phase afterward. A short-term release is covered only until the next LTS or STS ships, so 3007 is no longer supported for bugfix or CVE updates and gets no new patches. Treat any host still on 3007 as exposed and move it to 3008.
LTS and STS Lifecycle: Release Strategy and Support Policy
Since 3006, the Salt Project follows a release strategy of one LTS and one or more STS releases per year, and the support policy gives each type a different length of coverage. If you are unsure which to pick, choose the LTS. The release schedule adds one or two release candidates before each GA release, with features developed in the six months before it.
LTS Release: Long-Term Support for Stability
An LTS release gets active support for at least a full year plus one more year of CVE fixes. It is built for stability and for teams that need time to plan upgrades. The LTS release stays covered until a newer LTS ships, so there is always at least one. Long-term support here means two years of coverage in total.
STS Release: Short-Term Support for New Features
An STS release brings new features and the latest features between LTS builds. Its short-term support lasts only until the next LTS or STS ships, so choose it when you accept a little more risk for earlier access.
Support Levels Explained: When Support Ends
Each support level defines what the Salt Project ships, how long the support window lasts and how the support schedule changes over time. Once the active period closes, only security work continues, and then support ends altogether.
Active Support for Bug Fixes
Active support delivers regular point releases that target high and critical bugs. Point releases include earlier updates, so you can install the newest one without losing anything. Support for newer platforms is not added to an LTS in later point releases; it waits for the next major LTS, while an STS can gain it, which is one reason to leave an older LTS before its end of life. The supported operating systems guidance lists what each release covers.
CVE and Critical Support for Security Fixes
At this level the project may release fixes for selected CVEs, plus critical fixes for any breakage those patches cause. Fixes in newer branches are not back ported, so a patch landing in 3008 may never reach an older line. This is the final phase before a release reaches end of life, and 3006 gets it only until June 2027. Treat this security support as a countdown to migration.
Older Salt Version History: Unsupported Releases
Releases before 3006 followed a phase model, and all of them are past it. Phase 1 gave regular point releases, phase 2 offered on-demand fixes requested by VMware customers, and phase 3 covered CVEs only. Extended life support came last; for 3005 it ended on February 25, 2025, and no extended support program exists for anything older. Releases such as 3004 or 2019.2 are unsupported: there is no current maintenance and no sustaining maintenance either, so even critical CVEs go unpatched.
Planning Upgrades Before Salt Support Timelines End
Keeping your configuration management infrastructure on a supported LTS is the simplest way to stay ahead of the Salt end of life window. A short checklist helps:
- List every master and minion and note the release each one runs.
- Move 3007 and older hosts to 3008 first, because they receive no patches.
- Test 3008 on a staging copy of your Linux, Windows and Debian minions, checking each operating system package and Python dependency, before moving off 3006 or 3007.
- Follow the Salt Project roadmap, GitHub and community channels for changes to support timelines.
- Read the documentation for every point release before you deploy it.