Typo3 End of Life Dates
other
Typo3, a content management system, has been a staple for developers since its creation, providing a reliable platform for building and managing websites. The product is maintained by the Typo3 Association, a non-profit organization dedicated to ensuring the long-term sustainability of the software. Developers rely on Typo3 for its flexibility and scalability, making it an essential tool for creating complex web applications. With a history spanning several years, Typo3 has evolved to meet the changing needs of the developer community, with a focus on security and performance.
The end-of-life landscape for Typo3 is characterized by a total of 8 versions, with 6 of these versions having already reached the end of their support lifecycle. Currently, only 2 versions remain active, with the latest stable version being 13.4.31. Looking ahead, the next version to expire is version 13, which is scheduled to reach its end-of-life on December 31, 2027. This gives developers a clear timeline to plan their upgrades and migrations, ensuring minimal disruption to their applications. The most recent version to reach end-of-life was version 12, which ceased to be supported on April 30, 2026.
From a security perspective, Typo3 has a clean record, with no known Common Vulnerabilities and Exposures (CVEs) tracked. This means that there are no critical security patches that developers need to be concerned about. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status to report. Given this positive security posture, developers can focus on planning their upgrades and migrations, rather than worrying about addressing critical security issues. By staying informed about the end-of-life dates and security timelines for Typo3, developers can ensure the long-term health and stability of their applications.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 14 | Nov 25, 2025 | Dec 31, 2027 | Jun 30, 2029 | in 1072d | 14.3.5 | — | Active | |
| 13 | Jan 30, 2024 | Jun 30, 2026 | Dec 31, 2027 | in 525d | 13.4.33 | — | Active | |
| 12 | Oct 4, 2022 | Oct 31, 2024 | Apr 30, 2026 | 85d ago | 12.4.48 | — | EOL | |
| 11 LTS | Dec 22, 2020 | Mar 31, 2023 | Oct 31, 2024 | 631d ago | 11.5.53 | — | EOL | |
| 10 LTS | Jul 23, 2019 | Oct 31, 2021 | Apr 30, 2023 | 1181d ago | 10.4.59 | — | EOL | |
| 9 | Dec 12, 2017 | Apr 30, 2020 | Sep 30, 2021 | 1758d ago | 9.5.55 | — | EOL | |
| 8 | Mar 22, 2016 | Sep 30, 2018 | Mar 31, 2020 | 2306d ago | 8.7.58 | — | EOL | |
| 7 | Dec 2, 2014 | Apr 1, 2017 | Dec 1, 2018 | 2792d ago | 7.6.58 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
