HAProxy versions
HAProxy: update to 3.4.8, 3.3.18, 3.2.27, 3.0.31, 2.8.32 or 2.6.36. 3.1, 2.9, 2.7 and 2.5 and older have reached end of life in the lifecycle data.
Data: .
Which HAProxy branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 3.43 CVE records that this page reads | Fixes until 1 April 2031 | 3.4.8 | 3.4.8 (this branch) |
| 3.35 CVE records that this page reads | Fixes until 1 January 2027 | 3.3.18 | 3.3.18 (this branch) |
| 3.24 CVE records that this page reads | Fixes until 1 April 2030 | 3.2.27 | 3.2.27 (this branch) |
| 3.11 CVE record that this page reads | Ended on 1 January 2026 | None, the branch has ended | 3.2.27 (move to 3.2) |
| 3.02 CVE records that this page reads | Fixes until 1 April 2029 | 3.0.31 | 3.0.31 (this branch) |
| 2.9 | Ended on 21 March 2025 | None, the branch has ended | 3.0.31 (move to 3.0) |
| 2.8 | Fixes until 1 April 2028 | 2.8.32 | 2.8.32 (this branch) |
| 2.7 | Ended on 5 April 2024 | None, the branch has ended | 2.8.32 (move to 2.8) |
| 2.6 | Fixes until 1 April 2027 | 2.6.36 | 2.6.36 (this branch) |
| 2.5 | Ended on 2 May 2023 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 2.4 | Ended on 1 April 2026 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 2.3 | Ended on 27 July 2022 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 2.2 | Ended on 23 April 2025 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 2.1 | Ended on 18 March 2021 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 2.0 | Ended on 5 April 2024 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.9 | Ended on 31 July 2020 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.8 | Ended on 9 December 2022 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.7 | Ended on 1 October 2021 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.6 | Ended on 1 October 2020 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.5 | Ended on 10 January 2020 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.4 | Ended on 10 January 2020 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.3 | Ended on 14 March 2016 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.2 | Ended on 6 August 2011 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.1 | Ended on 29 January 2006 | None, the branch has ended | 2.6.36 (move to 2.6) |
| 1.0 | Ended on 30 December 2001 | None, the branch has ended | 2.6.36 (move to 2.6) |
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
This page reads 9 CVE records that the CVE Numbering Authorities MITRE and VulnCheck published and that name HAProxy. The fixes are from the 5 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.
No release of a branch that has ended is called safe here.
A range that holds only pre-releases (alphas, betas and release candidates) is left out. A record whose fix is a release candidate says so in its row, and the release candidate is not listed as a release.
4 records are not placed on a branch, so no branch or release row counts them: CVE-2025-32464, CVE-2026-33555, CVE-2026-55203 and CVE-2026-55204.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)