HAProxy End of Life Dates

server

Developers rely on server software to ensure seamless and secure connections between clients and servers. One such crucial tool is HAProxy, a reliable and widely-used solution created to provide high availability and load balancing. Maintained by a community-driven team, HAProxy has been a cornerstone of server management since its inception. The need to track end-of-life dates, supported versions, and security patch timelines for HAProxy arises from the fact that outdated software can pose significant security risks and compatibility issues. By staying informed about HAProxy's lifecycle, developers can plan upgrades and ensure their servers remain secure and efficient.

The current landscape of HAProxy versions reveals a total of 25 releases, with 19 of them having reached their end-of-life. This leaves 6 active versions that continue to receive support and security updates. Notably, the latest stable version, 2.8.24, is the current standard for new deployments. However, developers should be aware that version 3.3 is slated to reach its end-of-life on 2027-01-01, marking an important milestone in planning future upgrades. The most recent version to reach end-of-life was 2.4, which ceased to be supported on 2026-04-01. This dynamic landscape underscores the importance of monitoring version support timelines to avoid potential security vulnerabilities and compatibility issues.

Given the absence of tracked Common Vulnerabilities and Exposures (CVEs) for HAProxy, with both total and critical counts standing at 0, the security picture for this software appears to be very positive. Without a most affected version due to the lack of CVEs, the focus shifts towards maintaining up-to-date versions to ensure continued security and support. Developers should prioritize regular checks on the support status of their HAProxy versions and plan timely upgrades to avoid any potential security risks that may arise from using unsupported software. By doing so, they can leverage the benefits of HAProxy while minimizing exposure to vulnerabilities, ensuring their server infrastructure remains secure and reliable.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
3.4 LTSJun 3, 2026—Apr 1, 2031in 1621d3.4.7Active
3.3 Nov 26, 2025—Jan 1, 2027in 70d3.3.17EOL soon
3.2 LTSMay 28, 2025—Apr 1, 2030in 1256d3.2.26Active
3.1 Nov 26, 2024—Jan 1, 2026295d ago3.1.17EOL
3.0 LTSMay 29, 2024—Apr 1, 2029in 891d3.0.30Active
2.9 Dec 5, 2023—Mar 21, 2025581d ago2.9.15EOL
2.8 LTSMay 31, 2023—Apr 1, 2028in 526d2.8.31Active
2.7 Dec 1, 2022—Apr 5, 2024931d ago2.7.12EOL
2.6 LTSMay 31, 2022—Apr 1, 2027in 160d2.6.35Active
2.5 Nov 23, 2021—May 2, 20231270d ago2.5.14EOL
2.4 LTSMay 14, 2021—Apr 1, 2026205d ago2.4.36EOL
2.3 Nov 5, 2020—Jul 27, 20221549d ago2.3.21EOL
2.2 LTSJul 7, 2020—Apr 23, 2025548d ago2.2.34EOL
2.1 Nov 25, 2019—Mar 18, 20212045d ago2.1.12EOL
2.0 Jun 16, 2019—Apr 5, 2024931d ago2.0.35EOL
1.9 Dec 19, 2018—Jul 31, 20202275d ago1.9.16EOL
1.8 Nov 26, 2017—Dec 9, 20221414d ago1.8.31EOL
1.7 Nov 25, 2016—Oct 1, 20211848d ago1.7.14EOL
1.6 Oct 13, 2015—Oct 1, 20202213d ago1.6.16EOL
1.5 Jun 19, 2014—Jan 10, 20202478d ago1.5.19EOL
1.4 Feb 26, 2010—Jan 10, 20202478d ago1.4.27EOL
1.3 Jun 29, 2006—Mar 14, 20163875d ago1.3.28EOL
1.2 Nov 9, 2003—Aug 6, 20115557d ago1.2.18EOL
1.1 Mar 10, 2002—Jan 29, 20067572d ago1.1.34EOL
1.0 Dec 16, 2001—Dec 30, 20019063d ago1.0.2EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Popular alternatives

Frequently Asked Questions