HAProxy 3.3 · Version Status

HAProxy 3.3 End of Life Date

HAProxy 3.3 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

HAProxy 3.3 reaches end of life on January 1, 2027. Plan your migration now — 169 days remaining.
📅 Get reminded before HAProxy 3.3 reaches EOL on January 1, 2027 — alerts 90, 30 & 7 days out.
Google →
EOL Date
Jan 1, 2027
169 days remaining
Latest Release
3.3.12
Standard release
Release Date
Nov 26, 2025
HAProxy 3.3 series
← HAProxy 3.2 All HAProxy versions HAProxy 3.4 →
18 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
8/40
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 →
Recommended upgrade path
HAProxy 3.4
Latest release: 3.4.2 · EOL: Apr 1, 2031
View full HAProxy timeline →
Extended Support
Extended HAProxy 3.3 support is available

Commercial vendors offer security patches beyond EOL — compare your options.

Compare Options →
All HAProxy Versions
VersionLatestEOL DateStatus
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.3 end of life mean?

When HAProxy 3.3 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.3 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 3.3 reach end of life?
HAProxy 3.3 reached end of life on January 1, 2027. That is 169 days remaining.
Is HAProxy 3.3 still supported?
HAProxy 3.3 is still supported but approaching end of life on January 1, 2027. Begin planning your migration now.
What should I upgrade to from HAProxy 3.3?
The recommended upgrade from HAProxy 3.3 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 3.3 past EOL?
When HAProxy 3.3 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.
Data from endoflife.date API · Generated at build time · How we source data →