Complete end-of-life dates, support windows, and security status for all Typo3 versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7 | 7.6.58 | Dec 2, 2014 | Dec 1, 2018 | 2716 days past EOL | EOL |
| 8 | 8.7.58 | Mar 22, 2016 | Mar 31, 2020 | 2230 days past EOL | EOL |
| 9 | 9.5.55 | Dec 12, 2017 | Sep 30, 2021 | 1682 days past EOL | EOL |
| 10 LTS | 10.4.56 | Jul 23, 2019 | Apr 30, 2023 | 1105 days past EOL | EOL |
| 11 LTS | 11.5.50 | Dec 22, 2020 | Oct 31, 2024 | 555 days past EOL | EOL |
| 12 | 12.4.45 | Oct 4, 2022 | Apr 30, 2026 | 9 days past EOL | EOL |
| 13 | 13.4.28 | Jan 30, 2024 | Dec 31, 2027 | 601 days remaining | Active |
| 14 | 14.3.0 | Nov 25, 2025 | Jun 30, 2029 | 1148 days remaining | Active |
When a Typo3 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 Typo3 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 →