Typo3 13 · Version Status
Typo3 13 End of Life Date
Typo3 13 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Typo3 13 is actively supported. EOL date: December 31, 2027.
EOL Date
Dec 31, 2027
601 days remaining
Latest Release
13.4.28
Standard release
Release Date
Jan 30, 2024
Typo3 13 series
| Version | Latest | EOL Date | Status |
| 7 |
7.6.58 |
Dec 1, 2018 |
EOL |
| 8 |
8.7.58 |
Mar 31, 2020 |
EOL |
| 9 |
9.5.55 |
Sep 30, 2021 |
EOL |
| 10 LTS |
10.4.56 |
Apr 30, 2023 |
EOL |
| 11 LTS |
11.5.50 |
Oct 31, 2024 |
EOL |
| 12 |
12.4.45 |
Apr 30, 2026 |
EOL |
| → 13 |
13.4.28 |
Dec 31, 2027 |
Active |
| 14 |
14.3.0 |
Jun 30, 2029 |
Active |
What does Typo3 13 end of life mean?
When Typo3 13 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Typo3 13 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Typo3 14 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Typo3 13 reach end of life?
Typo3 13 reached end of life on December 31, 2027. That is 601 days remaining.
Is Typo3 13 still supported?
Yes, Typo3 13 is currently supported. The EOL date is December 31, 2027.
What should I upgrade to from Typo3 13?
The recommended upgrade from Typo3 13 is
Typo3 14 — the latest actively supported version. Check the
Typo3 full timeline for all supported versions.
What are the security risks of running Typo3 13 past EOL?
When Typo3 13 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Typo3 should migrate immediately or implement compensating controls.