← ← Back to all products
All badges & lifecycle API →
openSUSEEnd of Life (EOL) Dates & Support Status
Active
Operating SystemsLatest Version: 16.0Latest Release: N/A
openSUSE is a community-driven Linux distribution sponsored by SUSE, available in Leap and Tumbleweed editions.
Support summary
openSUSE currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
Oct 31, 2027
openSUSE 16.0 · 399 days left
Supported cycles
1
0 lts
Versions
21
Latest Version
16.0
Active Support
1
EOL
20
Lifecycle Timeline
Nov 16, 2016As of Sep 27, 2026
16.0Active · Oct 31, 2027
15.6EOL · Apr 30, 2026
15.5EOL · Dec 31, 2024
15.4EOL · Dec 7, 2023
15.3EOL · Dec 31, 2022
15.2EOL · Jan 4, 2022
15.1EOL · Feb 2, 2021
15.0EOL · Dec 3, 2019
42.3EOL · Jul 1, 2019
42.2EOL · Jan 26, 2018
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 16.0 | Oct 1, 2025 | Maintained | Oct 31, 2027 | 16.0 | No | Active |
| 15.6 | Jun 12, 2024 | Ended | Apr 30, 2026 | 15.6 | No | EOL |
| 15.5 | Jun 7, 2023 | Ended | Dec 31, 2024 | 15.5 | No | EOL |
| 15.4 | Jun 9, 2022 | Ended | Dec 7, 2023 | 15.4 | No | EOL |
| 15.3 | Jun 2, 2021 | Ended | Dec 31, 2022 | 15.3 | No | EOL |
| 15.2 | Jul 2, 2020 | Ended | Jan 4, 2022 | 15.2 | No | EOL |
| 15.1 | May 22, 2019 | Ended | Feb 2, 2021 | 15.1 | No | EOL |
| 15.0 | May 25, 2018 | Ended | Dec 3, 2019 | 15.0 | No | EOL |
| 42.3 | Jul 26, 2017 | Ended | Jul 1, 2019 | 42.3 | No | EOL |
| 42.2 | Nov 16, 2016 | Ended | Jan 26, 2018 | 42.2 | No | EOL |
| 42.1 | Nov 4, 2015 | Ended | May 17, 2017 | 42.1 | No | EOL |
| 13.2 | Nov 4, 2014 | Ended | Jan 17, 2017 | 13.2 | No | EOL |
| 13.1 | Jan 8, 2014 | Ended | Feb 3, 2016 | 13.1 | No | EOL |
| 12.3 | Mar 13, 2013 | Ended | Jan 29, 2015 | 12.3 | No | EOL |
| 12.2 | Sep 5, 2012 | Ended | Jan 15, 2014 | 12.2 | No | EOL |
| 12.1 | Nov 16, 2011 | Ended | May 15, 2013 | 12.1 | No | EOL |
| 11.4 | Mar 10, 2011 | Ended | Nov 5, 2012 | 11.4 | No | EOL |
| 11.3 | Jul 15, 2010 | Ended | Jan 20, 2012 | 11.3 | No | EOL |
| 11.2 | Nov 12, 2009 | Ended | May 12, 2011 | 11.2 | No | EOL |
| 11.1 | Dec 18, 2008 | Ended | Jan 14, 2011 | 11.1 | No | EOL |
| 11.0 | Jun 19, 2008 | Ended | Jul 26, 2010 | 11.0 | No | EOL |
Data sources
Embed this badge
Show openSUSE's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/opensuse/)HTML
<a href="https://eol.wiki/opensuse/"><img src="https://eol.wiki/badge/opensuse.svg" alt="openSUSE end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of openSUSE have reached end of life?
The following openSUSE versions have reached end of life and no longer receive security updates: 15.6, 15.5, 15.4, 15.3, 15.2, 15.1, 15.0, 42.3 (and 12 more). It is recommended to upgrade to a supported version.
Is it safe to continue using openSUSE 15.6?
openSUSE 15.6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of openSUSE?
The latest version of openSUSE is 16.0, released in the 16.0 release cycle.
How many versions of openSUSE are currently supported?
openSUSE currently has 1 actively supported version(s): 16.0.
When does openSUSE 16.0 reach end of life?
openSUSE 16.0 is scheduled to reach end of life on Oct 31, 2027.
What should I do when openSUSE reaches end of life?
When a openSUSE version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.