HAPROXY COVERAGE

HAProxy 2.4 and 3.1 are end of life. Your patching does not have to be.

HAProxy 3.1 reached end of life in the first quarter of 2026 and HAProxy 2.4 in the second, and the last releases are 3.1.17 and 2.4.36. OSSeva patches HAProxy Community Edition 2.4 and 3.1 after end of life, with Critical fixes within 48 hours. It does not patch HAProxy Enterprise or ALOHA.

Who it is forTeams running HAProxy Community Edition 2.4 or 3.1, as a standalone load balancer, in front of RabbitMQ or PostgreSQL clusters, or inside images, that cannot move to a supported branch yet
What you getSigned patched builds on the branch you run, with configuration unchanged. Assure adds an inventory of HAProxy instances and an upgrade plan to an LTS branch.
How it is pricedPer application. Ask for a quote.
What happens nextYou send your work email, we confirm your HAProxy version and how it is packaged, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

HAProxy branch status, read on 19 November 2026

Statuses and last releases are from the branch table on haproxy.org, which gives each end of life as a quarter. The dates are endoflife.date's, which put each at the first day of that quarter's first month.

BranchTypehaproxy.org statusEnd of lifeLast release
2.4LTSUnmaintained, 2026-Q21 Apr 20262.4.36 (3 Jul 2026)
3.1StableUnmaintained, 2026-Q11 Jan 20263.1.17 (19 Mar 2026)
2.6LTSCritical fixes only, 2027-Q21 Apr 20272.6.36 (18 Nov 2026)
2.8LTSCritical fixes only, 2028-Q21 Apr 20282.8.32 (18 Nov 2026)
3.0LTSLTS, 2029-Q21 Apr 20293.0.31 (18 Nov 2026)
3.2LTSLTS, 2030-Q21 Apr 20303.2.27 (18 Nov 2026)
3.3StableStable, 2027-Q11 Jan 20273.3.18 (18 Nov 2026)
3.4LTSLTS, 2031-Q21 Apr 20313.4.8 (18 Nov 2026)

haproxy.org says LTS branches are maintained for 5 years from release and odd-numbered stable branches for 12 to 18 months. Branches older than 2.4 are all listed as unmaintained.

haproxy.org branch table and branch policy →endoflife.date HAProxy data →HAProxy 2.4 changelog →

What 2.4 and 3.1 stopped receiving

HAProxy publishes each branch's changelog, so the gap between a closed branch and a live one can be read rather than assumed.

BranchFinal releaseWhat the changelog shows
2.42.4.36 (3 Jul 2026)The last entry reads "set the EOL for the 2.4 branch". The release also carries fixes for DNS name compression pointers, HTTP/1 h2c Upgrade values and an FCGI length overflow.
3.13.1.17 (19 Mar 2026)Eight months with no release. A stable branch is maintained for 12 to 18 months by the project's own policy, and 3.1 was released on 26 Nov 2024.
3.0 (for comparison)3.0.31 (18 Nov 2026)Six releases since 2.4 closed, 3.0.26 to 3.0.31, with 16 BUG/MAJOR and 114 BUG/MEDIUM commits. 2.4 receives none of them.

Counts are commit lines tagged BUG/MAJOR or BUG/MEDIUM in the 3.0 changelog dated after 3 July 2026, read on 19 November 2026. Not every fix applies to 2.4 code. No CVE is listed on this page because none was confirmed in both a CVE record and a vendor advisory: the HAProxy GitHub repository publishes no security advisories.

HAProxy 3.0 changelog →HAProxy 3.1 changelog →

Choosing a target branch when leaving 2.4 or 3.1

The branch table decides how long the next move lasts. These are the points that matter when you compare the supported lines.

  • 2.6 and 2.8 are the shortest hops from 2.4, but haproxy.org already labels both critical fixes only, with end of life on 1 April 2027 and 1 April 2028. Moving to 2.6 only lasts until its end of life on 1 April 2027.
  • 3.0, 3.2 and 3.4 are the LTS branches with full maintenance, ending 1 April 2029, 2030 and 2031. 3.4, released on 3 June 2026, has the longest run.
  • 3.3 is a stable branch with end of life on 1 January 2027. Moving from 3.1 to 3.3 repeats the same problem within two months, so a stable branch only suits teams that upgrade on every release.
  • haproxy.org says the first digit usually marks a breaking change such as the configuration format, but in practice rarely changes. Going from 2.4 to 3.x is a major version change, so run the existing configuration through a test instance and read the warnings before cutting over.
  • Where HAProxy sits in front of clustered services, patch before you move. Patroni and RabbitMQ high-availability setups commonly put HAProxy in front of the nodes, and changing the load balancer and the cluster in the same window is the riskier path.
  • OSSeva patches HAProxy Community Edition only. If you run HAProxy Enterprise or ALOHA, its vendor patches those, and OSSeva does not.

Sources: haproxy.org branch table and branch policy, read on 19 November 2026.

RabbitMQ support →PostgreSQL support →Apache Tomcat support →Traefik support →Patroni vs repmgr →

Why now

2.4 and 3.1 are marked unmaintained on haproxy.org

The branch table on haproxy.org lists 3.1 as unmaintained with an end of life of 2026-Q1 and 2.4 as unmaintained with 2026-Q2. endoflife.date dates them 1 January 2026 and 1 April 2026. The last 3.1 release is 3.1.17 from 19 March 2026, and the last 2.4 release is 2.4.36 from 3 July 2026.

The project closed 2.4 on purpose

The final 2.4.36 changelog entry reads "set the EOL for the 2.4 branch". Since then the 3.0 branch alone has shipped six releases, 3.0.26 to 3.0.31, with 16 BUG/MAJOR and 114 BUG/MEDIUM commits. Not every one touches 2.4 code, but 2.4 receives none of them.

2.6 and 2.8 are already critical fixes only

haproxy.org labels both LTS branches critical fixes only, with end of life in 2027-Q2 and 2028-Q2. The branches you would move to from 2.4 are on a short runway, so the target line matters as much as the date.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
2.4(LTS. EOL 1 Apr 2026 (haproxy.org: 2026-Q2))EOLSee advisories
3.1(Stable branch. EOL 1 Jan 2026 (haproxy.org: 2026-Q1))EOLSee advisories
2.6(LTS, critical fixes only. EOL 1 Apr 2027. Assessed case by case.)CurrentSee advisories
2.8(LTS, critical fixes only. EOL 1 Apr 2028. Assessed case by case.)CurrentSee advisories
3.0(LTS. EOL 1 Apr 2029. Assessed case by case.)CurrentSee advisories
3.2(LTS. EOL 1 Apr 2030. Assessed case by case.)CurrentSee advisories
3.3(Stable branch. EOL 1 Jan 2027. Assessed case by case.)CurrentSee advisories
3.4(LTS. EOL 1 Apr 2031. Assessed case by case.)CurrentSee advisories

Running a HAProxy version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for HAProxy 2.4 and 3.1 after end of life.

  • Backported security fixes for HAProxy Community Edition 2.4 and 3.1
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and an upgrade plan to a supported branch.

  • Everything in Patch
  • Inventory of HAProxy instances, including those inside images and appliances you build
  • Upgrade path assessment to 3.0, 3.2 or 3.4 LTS
  • SOC 2 / HIPAA attestation package
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 load balancer and backend health monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

When does HAProxy 2.4 reach end of life?

It already has. haproxy.org lists the 2.4 branch as unmaintained with an end of life of 2026-Q2, and endoflife.date gives 1 April 2026. The last release is 2.4.36, built on 3 July 2026, whose changelog ends with the entry that sets the end of life for the branch.

Is HAProxy 3.1 end of life?

Yes. haproxy.org lists 3.1 as unmaintained with an end of life of 2026-Q1, and endoflife.date gives 1 January 2026. 3.1 was a stable branch, which the project maintains for 12 to 18 months. The last release is 3.1.17, from 19 March 2026.

When does HAProxy 3.3 reach end of life?

haproxy.org lists 3.3 as stable with an end of life of 2027-Q1, and endoflife.date gives 1 January 2027. 3.3 is a stable branch, so it is the shortest-lived line in the current table.

Which HAProxy versions does OSSeva patch?

HAProxy Community Edition 2.4 and 3.1 after end of life. Other versions are assessed case by case through a version coverage check. OSSeva does not patch HAProxy Enterprise or ALOHA.

Who provides HAProxy support after end of life?

The HAProxy project stops releasing a branch at end of life. haproxy.org points users who want a long-term maintained package and commercial support to HAProxy Technologies and its HAProxy Enterprise product. Third-party providers, OSSeva among them, patch the community branches that ended. Ask each which branches it covers.

Which HAProxy branches are LTS?

Even-numbered branches. haproxy.org says LTS branches are maintained for 5 years from release and odd-numbered branches only for 12 to 18 months. The current LTS branches are 2.6, 2.8, 3.0, 3.2 and 3.4, with end of life in 2027-Q2, 2028-Q2, 2029-Q2, 2030-Q2 and 2031-Q2.

Is it safe to keep running HAProxy 2.4?

Only if the fixes keep coming from somewhere. HAProxy 2.4 gets no upstream release after 2.4.36, and a load balancer sits on the edge of the network, parsing HTTP from untrusted clients. OSSeva backports fixes for 2.4, with Critical issues patched within 48 hours.

How is OSSeva HAProxy support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get HAProxy patched and supported?

Tell us your HAProxy versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call