Traefik End of Life Dates
other
Developers rely on Traefik to manage and simplify their application delivery and networking. Created to address the complexities of modern application deployment, Traefik has been maintained by its community since its inception. The tool has gained popularity among developers due to its ability to streamline traffic management, providing a robust and scalable solution for a wide range of applications. With a strong focus on security and performance, Traefik has become an essential component in many development environments.
The landscape of Traefik's versions is characterized by a large number of releases, with a total of 21 versions available. Out of these, 19 versions have reached their end-of-life, leaving only 2 active versions currently supported. The latest stable version, 3.6.21, ensures that developers have access to the most up-to-date features and security patches. Although there is no next end-of-life date announced, the last version to reach its end-of-life was 2.11, which occurred on 2026-02-01, marking an important milestone in the product's lifecycle.
From a security perspective, Traefik's track record is impressive, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, and the product does not have a Known Exploited Vulnerability status. This exceptional security record is a testament to the dedication of the Traefik community in maintaining a secure and reliable product. Given this information, developers can confidently plan their upgrades and deployments, knowing that they are working with a secure and well-maintained tool, and can focus on delivering high-quality applications without worrying about underlying infrastructure vulnerabilities.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 3.7 | May 5, 2026 | — | No | — | 3.7.8 | — | Active | |
| 3.6 | Nov 7, 2025 | May 5, 2026 | May 5, 2026 | 80d ago | 3.6.23 | — | EOL | |
| 3.5 | Jul 23, 2025 | Nov 7, 2025 | Nov 7, 2025 | 259d ago | 3.5.6 | — | EOL | |
| 3.4 | May 5, 2025 | Jul 23, 2025 | Jul 23, 2025 | 366d ago | 3.4.5 | — | EOL | |
| 3.3 | Jan 6, 2025 | May 5, 2025 | May 5, 2025 | 445d ago | 3.3.7 | — | EOL | |
| 3.2 | Oct 28, 2024 | Jan 6, 2025 | Jan 6, 2025 | 564d ago | 3.2.5 | — | EOL | |
| 3.1 | Jul 15, 2024 | Oct 28, 2024 | Oct 28, 2024 | 634d ago | 3.1.7 | — | EOL | |
| 3.0 | Apr 29, 2024 | Jul 15, 2024 | Jul 15, 2024 | 739d ago | 3.0.4 | — | EOL | |
| 2.11 | Feb 12, 2024 | Apr 29, 2025 | Feb 1, 2026 | 173d ago | 2.11.52 | — | EOL | |
| 2.10 | Apr 24, 2023 | Feb 12, 2024 | Feb 12, 2024 | 893d ago | 2.10.7 | — | EOL | |
| 2.9 | Oct 3, 2022 | Apr 24, 2023 | Apr 24, 2023 | 1187d ago | 2.9.10 | — | EOL | |
| 2.8 | Jun 29, 2022 | Oct 3, 2022 | Oct 3, 2022 | 1390d ago | 2.8.8 | — | EOL | |
| 2.7 | May 24, 2022 | Jun 29, 2022 | Jun 29, 2022 | 1486d ago | 2.7.3 | — | EOL | |
| 2.6 | Jan 24, 2022 | May 24, 2022 | May 24, 2022 | 1522d ago | 2.6.7 | — | EOL | |
| 2.5 | Aug 17, 2021 | Jan 24, 2022 | Jan 24, 2022 | 1642d ago | 2.5.7 | — | EOL | |
| 2.4 | Jan 19, 2021 | Aug 17, 2021 | Aug 17, 2021 | 1802d ago | 2.4.14 | — | EOL | |
| 2.3 | Sep 23, 2020 | Jan 19, 2021 | Jan 19, 2021 | 2012d ago | 2.3.7 | — | EOL | |
| 2.2 | Mar 25, 2020 | Sep 23, 2020 | Sep 23, 2020 | 2130d ago | 2.2.11 | — | EOL | |
| 2.1 | Dec 11, 2019 | Mar 25, 2020 | Mar 25, 2020 | 2312d ago | 2.1.9 | — | EOL | |
| 2.0 | Sep 16, 2019 | Dec 11, 2019 | Dec 11, 2019 | 2417d ago | 2.0.7 | — | EOL | |
| 1.7 | Sep 24, 2018 | Dec 31, 2021 | Dec 31, 2021 | 1666d ago | 1.7.34 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
