SLES End of Life Dates
os
Developers rely on SUSE Linux Enterprise Server, a robust operating system, to power their critical workloads. Created by SUSE, a leading open-source software company, SLES has been a staple in the enterprise landscape for many years. The SUSE team maintains SLES, ensuring it remains a viable option for businesses seeking a secure and reliable operating system. By tracking SLES end-of-life dates, developers can plan their upgrades and migrations, minimizing potential security risks and ensuring uninterrupted service.
The SLES ecosystem comprises 25 versions, with 23 having already reached end-of-life. Currently, only 2 versions remain actively supported, emphasizing the need for developers to stay informed about the lifecycle of each release. The next significant milestone is the impending end-of-life date for version 16.0, scheduled for November 30, 2027. This follows the recent end-of-life date for version 15.6, which occurred on December 31, 2025. Staying abreast of these dates enables developers to proactively plan their upgrade strategies, avoiding potential security vulnerabilities and compatibility issues.
Given the absence of tracked CVEs, SLES presents a remarkably secure profile, with zero critical vulnerabilities reported. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status applies. Despite this favorable security posture, developers should remain vigilant and continue to monitor the SLES landscape for any emerging security concerns. By doing so, they can ensure the long-term stability and security of their SLES deployments, even as the operating system continues to evolve and mature. Regularly reviewing end-of-life dates and planning accordingly will help developers maintain a secure and up-to-date environment.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 16.0 | Nov 4, 2025 | — | Nov 30, 2027 | in 403d | — | — | Active | |
| 15.7 | Jun 17, 2025 | — | Jul 31, 2031 | in 1742d | — | — | Active | |
| 15.6 | Jun 26, 2024 | — | Dec 31, 2025 | 296d ago | — | — | EOL | |
| 15.5 | Jun 20, 2023 | — | Dec 31, 2024 | 661d ago | — | — | EOL | |
| 15.4 | Jun 21, 2022 | — | Dec 31, 2023 | 1027d ago | — | — | EOL | |
| 15.3 | Jun 22, 2021 | — | Dec 31, 2022 | 1392d ago | — | — | EOL | |
| 15.2 | Jul 21, 2020 | — | Dec 31, 2021 | 1757d ago | — | — | EOL | |
| 12.5 | Dec 9, 2019 | — | Oct 31, 2024 | 722d ago | — | — | EOL | |
| 15.1 | Jun 24, 2019 | — | Jan 31, 2021 | 2091d ago | — | — | EOL | |
| 12.4 | Dec 12, 2018 | — | Jun 30, 2020 | 2306d ago | — | — | EOL | |
| 15.0 | Jul 16, 2018 | — | Dec 31, 2019 | 2488d ago | — | — | EOL | |
| 12.3 | Sep 7, 2017 | — | Jun 30, 2019 | 2672d ago | — | — | EOL | |
| 12.2 | Nov 8, 2016 | — | Mar 31, 2018 | 3128d ago | — | — | EOL | |
| 12.1 | Dec 15, 2015 | — | May 31, 2017 | 3432d ago | — | — | EOL | |
| 11.4 | Jul 15, 2015 | — | Mar 31, 2019 | 2763d ago | — | — | EOL | |
| 12.0 | Oct 27, 2014 | — | Jun 30, 2016 | 3767d ago | — | — | EOL | |
| 11.3 | Jul 1, 2013 | — | Jan 31, 2016 | 3918d ago | — | — | EOL | |
| 11.2 | Feb 29, 2012 | — | Jan 31, 2014 | 4648d ago | — | — | EOL | |
| 10.4 | Apr 12, 2011 | — | Jul 31, 2013 | 4832d ago | — | — | EOL | |
| 11.1 | Jun 2, 2010 | — | Aug 31, 2012 | 5166d ago | — | — | EOL | |
| 10.3 | Oct 12, 2009 | — | Oct 11, 2011 | 5491d ago | — | — | EOL | |
| 11.0 | Mar 24, 2009 | — | Dec 31, 2010 | 5775d ago | — | — | EOL | |
| 10.2 | May 19, 2008 | — | Apr 11, 2010 | 6039d ago | — | — | EOL | |
| 10.1 | Jun 18, 2007 | — | Nov 30, 2008 | 6536d ago | — | — | EOL | |
| 10.0 | Jul 17, 2006 | — | Dec 31, 2007 | 6871d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
