HAProxy 3.x — End of Life

EOL soon High risk
EOL: Apr 1, 2031in 1621d5 releases in this series6 CVEs

HAProxy 3.x is partially supported: only 3.4, 3.3, 3.2, 3.0 still receive security fixes, the longest-lived (3.4) until Apr 1, 2031, in 1621 days. The most recent release in this series is 3.4.7. 6 CVEs are tracked for this series. 4 of them were published after the end of life of the affected cycle and will not get an official patch.

HAProxy 3.x — All releases

VersionReleasedActive supportEOL dateLatest patchStatusAlert me
3.4LTSJun 3, 2026—Apr 1, 20313.4.7Active
3.3Nov 26, 2025—Jan 1, 20273.3.17EOL soon
3.2LTSMay 28, 2025—Apr 1, 20303.2.26Active
3.1Nov 26, 2024—Jan 1, 20263.1.17EOL
3.0LTSMay 29, 2024—Apr 1, 20293.0.30Active

CVEs affecting HAProxy 3.x (23)

CVESeverityCVSSEPSSKEVCycleDescriptionPublished
CVE-2026-26081MEDIUM4.80.47%—3.2HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise…Jul 20, 2026
CVE-2026-26081MEDIUM4.80.47%—3.1HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise…Jul 20, 2026
CVE-2026-26081MEDIUM4.80.47%—3.3HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise…Jul 20, 2026
CVE-2026-26081MEDIUM4.80.47%—3.0HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise…Jul 20, 2026
CVE-2026-26080LOW3.70.54%—3.2HAProxy Community Edition 3.2.x through 3.3.x before 3.3.3 can enter a loop or crash because varint is mishandled. HAPro…Jul 20, 2026
CVE-2026-26080LOW3.70.54%—3.3HAProxy Community Edition 3.2.x through 3.3.x before 3.3.3 can enter a loop or crash because varint is mishandled. HAPro…Jul 20, 2026
CVE-2026-55204HIGH7.50.48%—3.2HAProxy through 3.4.0, fixed in commit 9a6d1fe, contains a null pointer dereference vulnerability in hpack_dht_insert()…Jun 18, 2026
CVE-2026-55204HIGH7.50.48%—3.1HAProxy through 3.4.0, fixed in commit 9a6d1fe, contains a null pointer dereference vulnerability in hpack_dht_insert()…Jun 18, 2026
CVE-2026-55204HIGH7.50.48%—3.3HAProxy through 3.4.0, fixed in commit 9a6d1fe, contains a null pointer dereference vulnerability in hpack_dht_insert()…Jun 18, 2026
CVE-2026-55204HIGH7.50.48%—3.0HAProxy through 3.4.0, fixed in commit 9a6d1fe, contains a null pointer dereference vulnerability in hpack_dht_insert()…Jun 18, 2026
CVE-2026-55204HIGH7.50.48%—3.4HAProxy through 3.4.0, fixed in commit 9a6d1fe, contains a null pointer dereference vulnerability in hpack_dht_insert()…Jun 18, 2026
CVE-2026-55203HIGH7.50.33%—3.0HAProxy through 3.4.0, fixed in commit 5985276, contains an integer overflow vulnerability in the fcgi_conn structure's …Jun 18, 2026
CVE-2026-55203HIGH7.50.33%—3.2HAProxy through 3.4.0, fixed in commit 5985276, contains an integer overflow vulnerability in the fcgi_conn structure's …Jun 18, 2026
CVE-2026-55203HIGH7.50.33%—3.1HAProxy through 3.4.0, fixed in commit 5985276, contains an integer overflow vulnerability in the fcgi_conn structure's …Jun 18, 2026
CVE-2026-55203HIGH7.50.33%—3.3HAProxy through 3.4.0, fixed in commit 5985276, contains an integer overflow vulnerability in the fcgi_conn structure's …Jun 18, 2026
CVE-2026-55203HIGH7.50.33%—3.4HAProxy through 3.4.0, fixed in commit 5985276, contains an integer overflow vulnerability in the fcgi_conn structure's …Jun 18, 2026
CVE-2026-33555MEDIUM4.00.57%—3.3An issue was discovered in HAProxy before 3.3.6. The HTTP/3 parser does not check that the received body length matches …Apr 13, 2026
CVE-2026-33555MEDIUM4.00.57%—3.2An issue was discovered in HAProxy before 3.3.6. The HTTP/3 parser does not check that the received body length matches …Apr 13, 2026
CVE-2026-33555MEDIUM4.00.57%—3.1An issue was discovered in HAProxy before 3.3.6. The HTTP/3 parser does not check that the received body length matches …Apr 13, 2026
CVE-2026-33555MEDIUM4.00.57%—3.0An issue was discovered in HAProxy before 3.3.6. The HTTP/3 parser does not check that the received body length matches …Apr 13, 2026
CVE-2025-11230HIGH7.5——3.0Inefficient algorithm complexity in mjson in HAProxy allows remote attackers to cause a denial of service via specially …Nov 19, 2025
CVE-2025-11230HIGH7.5——3.1Inefficient algorithm complexity in mjson in HAProxy allows remote attackers to cause a denial of service via specially …Nov 19, 2025
CVE-2025-11230HIGH7.5——3.2Inefficient algorithm complexity in mjson in HAProxy allows remote attackers to cause a denial of service via specially …Nov 19, 2025

Add a HAProxy 3 EOL badge to your README

Show your users which HAProxy version your project runs and whether it is still supported. The badge updates automatically. More formats and options →

HAProxy 3 EOL status
[![HAProxy 3 EOL status](https://eolcanary.com/badge/haproxy/3.svg)](https://eolcanary.com/explore/haproxy/3)

Frequently asked questions

Is HAProxy 3 end of life?

Partially. 1 of the 5 HAProxy 3.x releases have reached end of life. Still supported: 3.4, 3.3, 3.2, 3.0 (until April 1, 2031 at the latest).

What CVEs affect HAProxy 3?

There are 6 CVEs tracked for HAProxy 3.x. See the full list above with CVSS and EPSS scores.

What is the latest HAProxy 3 version?

The latest HAProxy 3.x patch release is 3.4.7, released on October 14, 2026. Always run the latest patch to benefit from all security fixes.

When was HAProxy 3 first released?

HAProxy 3.0 was released on May 29, 2024. See the full version timeline in the table above.

Is it safe to run HAProxy 3 in production?

Only on a supported release (3.4, 3.3, 3.2, 3.0). Support for HAProxy 3.4 ends on April 1, 2031. Make sure you run the latest patch (3.4.7) to have all security fixes applied.

Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA