SLES End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all SLES versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 10.0 | — | Jul 17, 2006 | Dec 31, 2007 | — | 6796 days past EOL | EOL |
| 10.1 | — | Jun 18, 2007 | Nov 30, 2008 | Dec 31, 2010 Long Term Service Pack Support (LTSS) (ended) |
6461 days past EOL | EOL |
| 10.2 | — | May 19, 2008 | Apr 11, 2010 | Apr 10, 2013 Long Term Service Pack Support (LTSS) (ended) |
5964 days past EOL | EOL |
| 11.0 | — | Mar 24, 2009 | Dec 31, 2010 | — | 5700 days past EOL | EOL |
| 10.3 | — | Oct 12, 2009 | Oct 11, 2011 | Oct 31, 2014 Long Term Service Pack Support (LTSS) (ended) |
5416 days past EOL | EOL |
| 11.1 | — | Jun 2, 2010 | Aug 31, 2012 | Aug 30, 2015 Long Term Service Pack Support (LTSS) (ended) |
5091 days past EOL | EOL |
| 10.4 | — | Apr 12, 2011 | Jul 31, 2013 | Jul 30, 2016 Long Term Service Pack Support (LTSS) (ended) |
4757 days past EOL | EOL |
| 11.2 | — | Feb 29, 2012 | Jan 31, 2014 | Jan 30, 2017 Long Term Service Pack Support (LTSS) (ended) |
4573 days past EOL | EOL |
| 11.3 | — | Jul 1, 2013 | Jan 31, 2016 | Jan 30, 2019 Long Term Service Pack Support (LTSS) (ended) |
3843 days past EOL | EOL |
| 12.0 | — | Oct 27, 2014 | Jun 30, 2016 | Jul 1, 2019 Long Term Service Pack Support (LTSS) (ended) |
3692 days past EOL | EOL |
| 11.4 | — | Jul 15, 2015 | Mar 31, 2019 | Mar 31, 2022 Long Term Service Pack Support (LTSS) (ended) |
2688 days past EOL | EOL |
| 12.1 | — | Dec 15, 2015 | May 31, 2017 | May 31, 2020 Long Term Service Pack Support (LTSS) (ended) |
3357 days past EOL | EOL |
| 12.2 | — | Nov 8, 2016 | Mar 31, 2018 | Mar 31, 2021 Long Term Service Pack Support (LTSS) (ended) |
3053 days past EOL | EOL |
| 12.3 | — | Sep 7, 2017 | Jun 30, 2019 | Jun 30, 2022 Long Term Service Pack Support (LTSS) (ended) |
2597 days past EOL | EOL |
| 15.0 | — | Jul 16, 2018 | Dec 31, 2019 | Dec 31, 2022 Long Term Service Pack Support (LTSS) (ended) |
2413 days past EOL | EOL |
| 12.4 | — | Dec 12, 2018 | Jun 30, 2020 | Jun 30, 2023 Long Term Service Pack Support (LTSS) (ended) |
2231 days past EOL | EOL |
| 15.1 | — | Jun 24, 2019 | Jan 31, 2021 | Jan 31, 2024 Long Term Service Pack Support (LTSS) (ended) |
2016 days past EOL | EOL |
| 12.5 | — | Dec 9, 2019 | Oct 31, 2024 | Oct 31, 2027 Long Term Service Pack Support (LTSS) |
647 days past EOL | EOL |
| 15.2 | — | Jul 21, 2020 | Dec 31, 2021 | Dec 31, 2024 Long Term Service Pack Support (LTSS) (ended) |
1682 days past EOL | EOL |
| 15.3 | — | Jun 22, 2021 | Dec 31, 2022 | Dec 31, 2025 Long Term Service Pack Support (LTSS) (ended) |
1317 days past EOL | EOL |
| 15.4 | — | Jun 21, 2022 | Dec 31, 2023 | Dec 31, 2026 Long Term Service Pack Support (LTSS) |
952 days past EOL | EOL |
| 15.5 | — | Jun 20, 2023 | Dec 31, 2024 | Dec 31, 2027 Long Term Service Pack Support (LTSS) |
586 days past EOL | EOL |
| 15.6 | — | Jun 26, 2024 | Dec 31, 2025 | Dec 31, 2028 Long Term Service Pack Support (LTSS) |
221 days past EOL | EOL |
| 15.7 | — | Jun 17, 2025 | Jul 31, 2031 | Jul 31, 2034 Long Term Service Pack Support (LTSS) |
1817 days remaining | Active |
| 16.0 | — | Nov 4, 2025 | Nov 30, 2027 | Nov 30, 2030 Long Term Service Pack Support (LTSS) |
478 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/sles)
What does SLES end of life mean for your organization?
When a version of SLES 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 SLES 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.
Your options when SLES reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL SLES versions. This is a bridge, not a permanent solution — plan your migration in parallel.
SLES has 23 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for SLES exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.