
HAProxy Technologies announced HAProxy Enterprise 3.4 on November 5, 2026. It is built on the open-source HAProxy 3.4 core and adds a long list of Enterprise-only features. The main ones are programmable UDP load balancing, finer control over the WAF, and built-in OpenTelemetry. If you run the community edition, the release is still worth a look, because two of its most practical changes come from the open-source core.
From the open-source core: backends without reloads
HAProxy 3.4 can create, update and delete whole backends through the Runtime API or the Data Plane API without a reload, and that includes mode tcp backends. This helps platforms that set up services from CI/CD pipelines or infrastructure-as-code tools. With no reload, fewer old processes hang around holding long-lived connections, and a bad edit to the full configuration file is less likely to block a deployment.
The second core change is a large-buffer pool. Enterprise 3.4 extends it to its own modules. The WAF and Bot Management modules now choose buffer sizes automatically, and you can still tune body limits per profile.
Programmable UDP load balancing
Most proxies are built around HTTP and TCP, so UDP services such as DNS or syslog often end up on separate tools. Enterprise 3.4 makes UDP a first-class traffic type:
- Per-datagram rules: new
udp-requestcontent rules can filter traffic, pick a server, set variables, track clients and rate-limit them. - Stick-table tracking: a new
trackkeyword adds stick-table counters for UDP, so you can limit noisy sources the same way you limit HTTP clients. - Protocol-aware health checks:
udp-checkunderstands DNS, RADIUS, NTP and syslog. A server is judged by whether it answers correctly, not just by whether its port is open.
The announcement’s example config uses directives such as udp-lb, dgram-bind, use-server, udp-request track-sc0, udp-request reject, udp-check send-binary and udp-check expect rbinary. Typical uses are DNS resolver pools, RADIUS servers for VPN and Wi-Fi logins, and central syslog collectors, all of which currently tend to use simple round-robin with no real health checking.
WAF, bot protection and CAPTCHA
- Inspection limits: you can now cap how much the Intelligent WAF Engine inspects: argument count, argument name length, inspected content and JSON argument count. Limits can be set globally, per WAF profile or on a single rule, with directives such as
iwe args-limit,iwe json-args-limitandiwe body-limit. HAProxy says the defaults work as before and that the limits do not change the inspection verdict. - XML body inspection: experimental and off by default. It parses XML request bodies as a stream and applies XML-specific rules.
- Logging: a compact CBOR format for WAF logs, and the option to send WAF logs somewhere other than your traffic logs.
- Self-hosted CAPTCHA: the CAPTCHA module now supports Altcha and Cap natively. You run the challenge and verification endpoints yourself, so you need no vendor site key or secret key. Challenges served, solved and abandoned show up in the access log.
- QUIC visibility: new sample fetches and a converter expose QUIC transport parameters, the negotiated version and connection-ID lengths, which you can use in rules.
Operations and compliance
- OpenTelemetry: the data plane sends traces, logs and metrics natively. This replaces the OpenTracing support in earlier versions.
- FIPS-ready builds: built on AWS-LC in FIPS mode, with no separate SKU or appliance needed.
- Remote certificate store: the
crt-storesection can fetch and refresh certificates and JWE key material from a remote source. - GSLB: adds support for TXT, CAA, NAPTR, RDATA and PTR records. A
cold-checkmode checks GSLB configuration syntax before changes are applied. - High availability: VRRP status can now be output as JSON, and the OVA images come with RADIUS, LDAP, Active Directory, Kerberos, OIDC and SAML authentication pre-installed.
Before you upgrade
| Item | Status in 3.4 | Move to |
|---|---|---|
| OWASP CRS v3 | No longer supported, still works | CRS v4 in CRS compatibility mode |
| Legacy ModSecurity WAF module | Deprecated, removal planned for 3.5 | HAProxy Enterprise WAF |
| Per-module body directives | Deprecated, still works | WAF large-buffer directives |
- List which deprecated items your configs use. You can migrate from CRS v3 to v4 before or after the upgrade. Plan the ModSecurity migration now, because the module is removed in 3.5.
- If you use OpenTracing, plan the move to the new OpenTelemetry support.
- Install 3.4 in staging by following HAProxy’s Enterprise upgrade guide. Run its configuration check mode (
-c) against a copy of your production configuration, and read every warning. - Move traffic over with your normal hitless reload process, then watch error rates, WAF logs and health check status before you roll out further.
If you are staying on an older branch for now, make sure you are on the fixed builds from HAProxy’s October 2026 security bulletin. That bulletin covers CVE-2026-110354 and CVE-2026-110353, which can exhaust CPU through HTTP/1 chunk parsing and HTTP/2 PING frames. Fixed Enterprise builds include 3.3r1-377.1005 and 3.2r1-378.1259.
How TechProvidence can help
TechProvidence designs, upgrades and supports HAProxy and NGINX load balancing for businesses, including WAF tuning, health check design, zero-downtime reloads and staged version upgrades. If you are planning a move to 3.4 or a migration away from ModSecurity, contact us.
Source: HAProxy Technologies blog


