Complete end-of-life dates, support windows, and security status for all Contao versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.5 LTS | 3.5.40 | Jun 5, 2015 | May 31, 2019 | 2535 days past EOL | EOL |
| 4.4 LTS | 4.4.57 | Jun 15, 2017 | Dec 14, 2021 | 1607 days past EOL | EOL |
| 4.9 LTS | 4.9.42 | Feb 18, 2020 | Feb 14, 2024 | 815 days past EOL | EOL |
| 4.10 | 4.10.7 | Aug 18, 2020 | Feb 14, 2021 | 1910 days past EOL | EOL |
| 4.11 | 4.11.9 | Feb 17, 2021 | Aug 14, 2021 | 1729 days past EOL | EOL |
| 4.12 | 4.12.7 | Aug 19, 2021 | Jan 14, 2022 | 1576 days past EOL | EOL |
| 4.13 LTS | 4.13.58 | Feb 17, 2022 | Feb 14, 2026 | 84 days past EOL | EOL |
| 5.0 | 5.0.10 | Aug 18, 2022 | Feb 14, 2023 | 1180 days past EOL | EOL |
| 5.1 | 5.1.11 | Feb 16, 2023 | Aug 14, 2023 | 999 days past EOL | EOL |
| 5.2 | 5.2.10 | Aug 15, 2023 | Feb 14, 2024 | 815 days past EOL | EOL |
| 5.3 LTS | 5.3.46 | Feb 16, 2024 | Feb 14, 2028 | 646 days remaining | Active |
| 5.4 | 5.4.14 | Aug 15, 2024 | Feb 14, 2025 | 449 days past EOL | EOL |
| 5.5 | 5.5.16 | Feb 18, 2025 | Aug 14, 2025 | 268 days past EOL | EOL |
| 5.6 | 5.6.11 | Aug 18, 2025 | Feb 14, 2026 | 84 days past EOL | EOL |
| 5.7 LTS | 5.7.4 | Feb 18, 2026 | Feb 14, 2030 | 1377 days remaining | Active |
When a Contao 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 Contao 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 →