TYPO3 8 · Version Status
TYPO3 8 End of Life Date
TYPO3 8 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
TYPO3 8 is past end of life. This version no longer receives security patches. 2412 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 31, 2020
2412 days past EOL
Latest Release
8.7.58
Standard release
Release Date
Mar 22, 2016
TYPO3 8 series
Extended Support
Mar 31, 2024
TYPO3 ELTS · paid · ended
Where these dates come from
End of lifeMar 31, 2020endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportSep 30, 2018endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of extended supportMar 31, 2024endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseMar 22, 2016endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
TYPO3 8 was released on March 22, 2016 and support ended on March 31, 2020 — a supported lifespan of 4 years, in line with the 3 years and 10 months median for TYPO3 releases. It was not an LTS release; TYPO3 reserves longer patch windows for its LTS releases. Its latest release on record is 8.7.58, published February 14, 2024 — 3 years and 11 months after the published end-of-life date. It has been past its end-of-life date for 6 years and 7 months. 4 newer TYPO3 releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended TYPO3 8 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| 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.62 |
Apr 30, 2023 |
EOL |
| 11 LTS |
11.5.56 |
Oct 31, 2024 |
EOL |
| 12 |
12.4.51 |
Apr 30, 2026 |
EOL |
| 13 |
13.4.37 |
Dec 31, 2027 |
Active |
| 14 |
14.3.10 |
Jun 30, 2029 |
Active |
What does TYPO3 8 end of life mean?
When TYPO3 8 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running TYPO3 8 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to TYPO3 14 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does TYPO3 8 reach end of life?
TYPO3 8 reached end of life on March 31, 2020. This version is no longer receiving security patches.
Is TYPO3 8 still supported?
No. TYPO3 8 reached end of life on March 31, 2020 and is no longer receiving security patches.
What should I upgrade to from TYPO3 8?
The recommended upgrade from TYPO3 8 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 8 past EOL?
Since TYPO3 8 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL TYPO3 should migrate immediately or implement compensating controls.