CVE-2026-109575: Critical severity HAProxy Data Plane API vulnerability
In HAProxy Data Plane API 2.2.0 through 3.4.3 (and corresponding Enterprise Edition releases), Server.ConfigureAPI() has process-global authentication logic that improperly drops security controls across multiple transport types. When a TLS Certificate Authority (tlsca) is configured and a numeric TLS port (tlsport) is specified, the application globally disables Basic authentication on its shared internal request handler. Because this handler is shared concurrently among HTTP, HTTPS, and UNIX domain socket listeners, and mutual TLS (mTLS) client certificate verification (tls.RequireAndVerifyClientCert) is enforced exclusively on the HTTPS server path, all other simultaneously active non-mTLS listeners fail open. Consequently, an unauthenticated attacker capable of reaching an affected HTTP or UNIX management endpoint can completely bypass credentials to gain full API administrative access. This allows unauthorized remote or local actors to read sensitive, cleartext HAProxy configuration data or replace the managed configuration entirely via the raw configuration endpoint. This has been fixed in versions 3.4.4, 3.3.9, 3.2.17, 3.0.25, 2.9.29, and their respective EE backports by migrating to a per-request TLS connection-state validation model.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
HAProxy Data Plane APIto a version that resolves this vulnerability.Fixed in 3.4.4 - Upgrade
Upgrade
HAProxy Data Plane APIto a version that resolves this vulnerability.Fixed in 3.3.9 - Upgrade
Upgrade
HAProxy Data Plane APIto a version that resolves this vulnerability.Fixed in 3.2.17 - Upgrade
Upgrade
HAProxy Data Plane APIto a version that resolves this vulnerability.Fixed in 3.0.25 - Upgrade
Upgrade
HAProxy Data Plane APIto a version that resolves this vulnerability.Fixed in 2.9.29
Event History
Frequently Asked Questions
Which deployments are exposed to unauthenticated access?
Exposure requires a configured TLS Certificate Authority (tls_ca), a numeric TLS port (tls_port), and a simultaneously active HTTP or UNIX domain socket management listener. The HTTPS path enforces mTLS client-certificate verification, but the shared handler causes the other non-mTLS listeners to fail open.
What does an attacker need to exploit this issue?
An attacker needs only network access to an affected HTTP management endpoint or local access to an affected UNIX management socket. No Basic-authentication credentials are required under the affected configuration.
What access can a successful attacker obtain?
A successful attacker gains full API administrative access. They can read sensitive cleartext HAProxy configuration data and can replace the managed configuration through the raw configuration endpoint.
Which releases contain the fix?
Fixed releases are 3.4.4, 3.3.9, 3.2.17, 3.0.25, and 2.9.29, along with their respective Enterprise Edition backports.