Nixos End of Life Dates
other
Developers rely on Nixos, a unique Linux distribution, to create reproducible and declarative configurations for their systems. Nixos was first introduced in 2003 and is maintained by the Nixos Foundation, a community-driven organization. The foundation ensures that Nixos stays up-to-date with the latest security patches and features, which is why developers use it to manage their systems. By tracking Nixos end-of-life dates, supported versions, and security patch timelines, developers can plan their upgrades and minimize potential security risks.
The end-of-life landscape for Nixos is characterized by a large number of versions, with 25 releases in total. Out of these, 23 versions have already reached their end-of-life, leaving only 2 active versions. The next version to expire is 25.11, which will reach its end-of-life on 2026-06-30. This means that developers still using this version should start planning their upgrades to ensure they remain supported. The last version to reach its end-of-life was 25.05, which expired on 2025-12-31. By keeping track of these dates, developers can avoid using unsupported versions and reduce their exposure to potential security vulnerabilities.
The security picture for Nixos is currently very positive, with 0 CVEs tracked and 0 critical CVEs. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status applies. This suggests that Nixos has a strong security track record, which is beneficial for developers who rely on it. However, this does not mean that developers should be complacent, and they should continue to monitor the security situation and plan their upgrades accordingly to ensure they remain secure. By staying on top of end-of-life dates and security patches, developers can ensure the continued stability and security of their systems.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 26.05 | May 30, 2026 | — | Dec 31, 2026 | in 69d | — | — | EOL soon | |
| 25.11 | Nov 30, 2025 | — | Jun 30, 2026 | 115d ago | — | — | EOL | |
| 25.05 | May 23, 2025 | — | Dec 31, 2025 | 296d ago | — | — | EOL | |
| 24.11 | Nov 30, 2024 | — | Jun 30, 2025 | 480d ago | — | — | EOL | |
| 24.05 | May 31, 2024 | — | Dec 31, 2024 | 661d ago | — | — | EOL | |
| 23.11 | Nov 29, 2023 | — | Jun 30, 2024 | 845d ago | — | — | EOL | |
| 23.05 | May 31, 2023 | — | Dec 31, 2023 | 1027d ago | — | — | EOL | |
| 22.11 | Nov 30, 2022 | — | Jun 30, 2023 | 1211d ago | — | — | EOL | |
| 22.05 | May 30, 2022 | — | Dec 31, 2022 | 1392d ago | — | — | EOL | |
| 21.11 | Nov 30, 2021 | — | Jun 30, 2022 | 1576d ago | — | — | EOL | |
| 21.05 | May 31, 2021 | — | Dec 31, 2021 | 1757d ago | — | — | EOL | |
| 20.09 | Oct 27, 2020 | — | Jun 30, 2021 | 1941d ago | — | — | EOL | |
| 20.03 | Apr 20, 2020 | — | Oct 30, 2020 | 2184d ago | — | — | EOL | |
| 19.09 | Oct 9, 2019 | — | Apr 30, 2020 | 2367d ago | — | — | EOL | |
| 19.03 | Apr 11, 2019 | — | Oct 30, 2019 | 2550d ago | — | — | EOL | |
| 18.09 | Oct 5, 2018 | — | Apr 30, 2019 | 2733d ago | — | — | EOL | |
| 18.03 | Apr 4, 2018 | — | Oct 30, 2018 | 2915d ago | — | — | EOL | |
| 17.09 | Sep 29, 2017 | — | Apr 30, 2018 | 3098d ago | — | — | EOL | |
| 17.03 | Mar 31, 2017 | — | Oct 30, 2017 | 3280d ago | — | — | EOL | |
| 16.09 | Sep 30, 2016 | — | Apr 30, 2017 | 3463d ago | — | — | EOL | |
| 16.03 | Mar 31, 2016 | — | Oct 30, 2016 | 3645d ago | — | — | EOL | |
| 15.09 | Sep 30, 2015 | — | Apr 30, 2016 | 3828d ago | — | — | EOL | |
| 14.12 | Dec 30, 2014 | — | Sep 30, 2015 | 4041d ago | — | — | EOL | |
| 14.04 | Apr 30, 2014 | — | Jan 31, 2015 | 4283d ago | — | — | EOL | |
| 13.10 | Oct 31, 2013 | — | May 31, 2014 | 4528d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
