Traefik End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Traefik versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.7 | 1.7.34 | Sep 24, 2018 | Dec 31, 2021 | 1635 days past EOL | EOL |
| 2.0 | 2.0.7 | Sep 16, 2019 | Dec 11, 2019 | 2386 days past EOL | EOL |
| 2.1 | 2.1.9 | Dec 11, 2019 | Mar 25, 2020 | 2281 days past EOL | EOL |
| 2.2 | 2.2.11 | Mar 25, 2020 | Sep 23, 2020 | 2099 days past EOL | EOL |
| 2.3 | 2.3.7 | Sep 23, 2020 | Jan 19, 2021 | 1981 days past EOL | EOL |
| 2.4 | 2.4.14 | Jan 19, 2021 | Aug 17, 2021 | 1771 days past EOL | EOL |
| 2.5 | 2.5.7 | Aug 17, 2021 | Jan 24, 2022 | 1611 days past EOL | EOL |
| 2.6 | 2.6.7 | Jan 24, 2022 | May 24, 2022 | 1491 days past EOL | EOL |
| 2.7 | 2.7.3 | May 24, 2022 | Jun 29, 2022 | 1455 days past EOL | EOL |
| 2.8 | 2.8.8 | Jun 29, 2022 | Oct 3, 2022 | 1359 days past EOL | EOL |
| 2.9 | 2.9.10 | Oct 3, 2022 | Apr 24, 2023 | 1156 days past EOL | EOL |
| 2.10 | 2.10.7 | Apr 24, 2023 | Feb 12, 2024 | 862 days past EOL | EOL |
| 2.11 | 2.11.50 | Feb 12, 2024 | Feb 1, 2026 | 142 days past EOL | EOL |
| 3.0 | 3.0.4 | Apr 29, 2024 | Jul 15, 2024 | 708 days past EOL | EOL |
| 3.1 | 3.1.7 | Jul 15, 2024 | Oct 28, 2024 | 603 days past EOL | EOL |
| 3.2 | 3.2.5 | Oct 28, 2024 | Jan 6, 2025 | 533 days past EOL | EOL |
| 3.3 | 3.3.7 | Jan 6, 2025 | May 5, 2025 | 414 days past EOL | EOL |
| 3.4 | 3.4.5 | May 5, 2025 | Jul 23, 2025 | 335 days past EOL | EOL |
| 3.5 | 3.5.6 | Jul 23, 2025 | Nov 7, 2025 | 228 days past EOL | EOL |
| 3.6 | 3.6.21 | Nov 7, 2025 | TBD | Supported | Active |
| 3.7 | 3.7.5 | Apr 22, 2026 | TBD | Supported | Active |
What does Traefik end of life mean for your organization?
When a version of Traefik 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 Traefik 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Traefik versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →