Haproxy 3.2 · Version Status
Haproxy 3.2 End of Life Date
Haproxy 3.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Haproxy 3.2 is actively supported. EOL date: April 1, 2030.
EOL Date
Apr 1, 2030
1423 days remaining
Latest Release
3.2.18
LTS release
Release Date
May 28, 2025
Haproxy 3.2 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.2 |
Dec 30, 2001 |
EOL |
| 1.1 |
1.1.34 |
Jan 29, 2006 |
EOL |
| 1.2 |
1.2.18 |
Aug 6, 2011 |
EOL |
| 1.3 |
1.3.28 |
Mar 14, 2016 |
EOL |
| 1.4 |
1.4.27 |
Jan 10, 2020 |
EOL |
| 1.5 |
1.5.19 |
Jan 10, 2020 |
EOL |
| 1.6 |
1.6.16 |
Oct 1, 2020 |
EOL |
| 1.7 |
1.7.14 |
Oct 1, 2021 |
EOL |
What does Haproxy 3.2 end of life mean?
When Haproxy 3.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Haproxy 3.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Haproxy 3.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Haproxy 3.2 reach end of life?
Haproxy 3.2 reached end of life on April 1, 2030. That is 1423 days remaining.
Is Haproxy 3.2 still supported?
Yes, Haproxy 3.2 is currently supported. The EOL date is April 1, 2030.
What should I upgrade to from Haproxy 3.2?
The recommended upgrade from Haproxy 3.2 is
Haproxy 3.3 — the latest actively supported version. Check the
Haproxy full timeline for all supported versions.
What are the security risks of running Haproxy 3.2 past EOL?
When Haproxy 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Haproxy should migrate immediately or implement compensating controls.