Libreoffice End of Life Dates
other
Developers rely on Libreoffice for their document processing needs, and understanding its lifecycle is crucial for maintaining security and compatibility. Created as a free and open-source alternative to proprietary office suites, Libreoffice has been maintained by The Document Foundation since its inception. The community-driven approach has led to widespread adoption, with developers using it due to its flexibility, customizability, and cost-effectiveness. Libreoffice's end-of-life tracking is essential for planning upgrades and ensuring that systems remain supported and secure.
The end-of-life landscape for Libreoffice is characterized by a total of 9 versions, with 8 of them having already reached the end of their support lifecycle. Currently, only 1 version remains actively supported, emphasizing the need for developers to stay up-to-date with the latest stable version, which is 26.2.3. Looking ahead, the next version slated to reach end-of-life is 26.2, with its support ending on 2026-11-30. This deadline serves as a critical reminder for developers to plan their upgrades and migrations accordingly, especially considering the recent end-of-life date that passed on 2026-06-12 for version 25.8.
From a security perspective, Libreoffice has a remarkably clean track record, with a total of 0 CVEs tracked and 0 critical vulnerabilities reported. As a result, there is no most affected version, and the product does not have a Known Exploited Vulnerability status. This exemplary security posture is a testament to the diligence of The Document Foundation and the Libreoffice community. Nevertheless, developers should still prioritize staying current with the latest versions to ensure they have access to the newest features and any future security patches, thereby maintaining the integrity and reliability of their systems.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 26.2 | Feb 4, 2026 | — | Nov 30, 2026 | in 129d | 26.2.4 | — | Active | |
| 25.8 | Jul 9, 2025 | — | Jun 12, 2026 | 42d ago | 25.8.7 | — | EOL | |
| 25.2 | Dec 22, 2024 | — | Nov 30, 2025 | 236d ago | 25.2.7.2 | — | EOL | |
| 24.8 | Jul 9, 2024 | — | Jun 12, 2025 | 407d ago | 24.8.7.2 | — | EOL | |
| 24.2 | Jan 8, 2024 | — | Nov 30, 2024 | 601d ago | 24.2.7.2 | — | EOL | |
| 7.6 | Jul 10, 2023 | — | Jun 12, 2024 | 772d ago | 7.6.7.2 | — | EOL | |
| 7.5 | Dec 26, 2022 | — | Dec 7, 2023 | 960d ago | 7.5.9.2 | — | EOL | |
| 7.4 | Jul 10, 2022 | — | Jun 12, 2023 | 1138d ago | 7.4.7.2 | — | EOL | |
| 7.3 | Dec 23, 2021 | — | Nov 30, 2022 | 1332d ago | 7.3.7.2 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
