HAProxy 1.1 · Version Status
HAProxy 1.1 End of Life Date
HAProxy 1.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
HAProxy 1.1 is past end of life. This version no longer receives security patches. 7507 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 29, 2006
7507 days past EOL
Latest Release
1.1.34
Standard release
Release Date
Mar 10, 2002
HAProxy 1.1 series
Lifecycle detail
HAProxy 1.1 was released on March 10, 2002 and support ended on January 29, 2006 — a supported lifespan of 3 years and 11 months, shorter than the 4 years and 10 months median for HAProxy releases. It was not an LTS release; HAProxy reserves longer patch windows for its LTS versions. The last patch it will ever receive is 1.1.34, published January 29, 2006 — on the day support ended. It has been without security patches for 20 years and 7 months. 22 newer HAProxy releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended HAProxy 1.1 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| 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 1.1 end of life mean?
When HAProxy 1.1 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 1.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to HAProxy 3.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does HAProxy 1.1 reach end of life?
HAProxy 1.1 reached end of life on January 29, 2006. This version is no longer receiving security patches.
Is HAProxy 1.1 still supported?
No. HAProxy 1.1 reached end of life on January 29, 2006 and is no longer receiving security patches.
What should I upgrade to from HAProxy 1.1?
The recommended upgrade from HAProxy 1.1 is
HAProxy 3.4 — the latest actively supported version. Check the
HAProxy full timeline for all supported versions.
What are the security risks of running HAProxy 1.1 past EOL?
When HAProxy 1.1 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.