Complete end-of-life dates, support windows, and security status for all Haproxy versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.2 | Dec 16, 2001 | Dec 30, 2001 | 8896 days past EOL | EOL |
| 1.1 | 1.1.34 | Mar 10, 2002 | Jan 29, 2006 | 7405 days past EOL | EOL |
| 1.2 | 1.2.18 | Nov 9, 2003 | Aug 6, 2011 | 5390 days past EOL | EOL |
| 1.3 | 1.3.28 | Jun 29, 2006 | Mar 14, 2016 | 3708 days past EOL | EOL |
| 1.4 | 1.4.27 | Feb 26, 2010 | Jan 10, 2020 | 2311 days past EOL | EOL |
| 1.5 | 1.5.19 | Jun 19, 2014 | Jan 10, 2020 | 2311 days past EOL | EOL |
| 1.6 | 1.6.16 | Oct 13, 2015 | Oct 1, 2020 | 2046 days past EOL | EOL |
| 1.7 | 1.7.14 | Nov 25, 2016 | Oct 1, 2021 | 1681 days past EOL | EOL |
| 1.8 | 1.8.31 | Nov 26, 2017 | Dec 9, 2022 | 1247 days past EOL | EOL |
| 1.9 | 1.9.16 | Dec 19, 2018 | Jul 31, 2020 | 2108 days past EOL | EOL |
| 2.0 | 2.0.35 | Jun 16, 2019 | Apr 5, 2024 | 764 days past EOL | EOL |
| 2.1 | 2.1.12 | Nov 25, 2019 | Mar 18, 2021 | 1878 days past EOL | EOL |
| 2.2 LTS | 2.2.34 | Jul 7, 2020 | Apr 23, 2025 | 381 days past EOL | EOL |
| 2.3 | 2.3.21 | Nov 5, 2020 | Jul 27, 2022 | 1382 days past EOL | EOL |
| 2.4 LTS | 2.4.34 | May 14, 2021 | Apr 1, 2026 | 38 days past EOL | EOL |
| 2.5 | 2.5.14 | Nov 23, 2021 | May 2, 2023 | 1103 days past EOL | EOL |
| 2.6 LTS | 2.6.28 | May 31, 2022 | Apr 1, 2027 | 327 days remaining | Active |
| 2.7 | 2.7.12 | Dec 1, 2022 | Apr 5, 2024 | 764 days past EOL | EOL |
| 2.8 LTS | 2.8.23 | May 31, 2023 | Apr 1, 2028 | 693 days remaining | Active |
| 2.9 | 2.9.15 | Dec 5, 2023 | Mar 21, 2025 | 414 days past EOL | EOL |
| 3.0 LTS | 3.0.22 | May 29, 2024 | Apr 1, 2029 | 1058 days remaining | Active |
| 3.1 | 3.1.17 | Nov 26, 2024 | Jan 1, 2026 | 128 days past EOL | EOL |
| 3.2 LTS | 3.2.18 | May 28, 2025 | Apr 1, 2030 | 1423 days remaining | Active |
| 3.3 | 3.3.9 | Nov 26, 2025 | Jan 1, 2027 | 237 days remaining | Active |
When a Haproxy 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 Haproxy 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 →