Complete end-of-life dates, support windows, and security status for all Libreoffice versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.3 | 7.3.7.2 | Dec 23, 2021 | Nov 30, 2022 | 1256 days past EOL | EOL |
| 7.4 | 7.4.7.2 | Jul 10, 2022 | Jun 12, 2023 | 1062 days past EOL | EOL |
| 7.5 | 7.5.9.2 | Dec 26, 2022 | Dec 7, 2023 | 884 days past EOL | EOL |
| 7.6 | 7.6.7.2 | Jul 10, 2023 | Jun 12, 2024 | 696 days past EOL | EOL |
| 24.2 | 24.2.7.2 | Jan 8, 2024 | Nov 30, 2024 | 525 days past EOL | EOL |
| 24.8 | 24.8.7.2 | Jul 9, 2024 | Jun 12, 2025 | 331 days past EOL | EOL |
| 25.2 | 25.2.7.2 | Dec 22, 2024 | Nov 30, 2025 | 160 days past EOL | EOL |
| 25.8 | 25.8.6.2 | Jul 9, 2025 | Jun 12, 2026 | 34 days remaining | Warning |
| 26.2 | 26.2.2.2 | Feb 4, 2026 | Nov 30, 2026 | 205 days remaining | Active |
When a Libreoffice version 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 Libreoffice 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →