CVE-2026-109575In 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 ac…
Updated under an hour ago ()
Does this affect you?
It affects HAProxy Data Plane API EE and 1 other product. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.36%, higher than 28% of scored CVEs.
Do this next
Free account, 1 product
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 (tls_ca) is configured and a numeric TLS port (tls_port) 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.
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-306
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.36% (percentile 28)
- Assigned by
- mitre
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 13, 2026
- First seen by InfoSec Signals
- Oct 12, 2026
Affected products
HAProxy Data Plane API EE haproxy:data_plane_api_ee (from the name) | from 2.2.0-ee1 through 2.9.28-ee1; fixed at 2.9.29-ee1; from 3.0-ee through 3.0.24-ee1; fixed at 3.0.25-ee1; from 3.1-ee through 3.2.16-ee1; fixed at 3.2.17-ee1; from 3.3-ee through 3.3.8-ee1; fixed at 3.3.9-ee1; from 3.4-ee through 3.4.3-ee2; fixed at 3.4.4-ee1 | CNA record |
HAProxy Data Plane API CE haproxy:data_plane_api_ce (from the name) | from 2.2.0 through 2.9.28; fixed at 2.9.29; from 3.0.0 through 3.0.24; fixed at 3.0.25; from 3.1.0 through 3.2.16; fixed at 3.2.17; from 3.3.0 through 3.3.8; fixed at 3.3.9; from 3.4.0 through 3.4.3; fixed at 3.4.4 | CNA record |
References
- https://www.haproxy.com/documentation/haproxy-data-plane-api/
- https://www.haproxy.com/documentation/haproxy-data-plane-api/community/changelog/#version-3.4
- https://github.com/haproxytech/dataplaneapi/commit/c3ae4e3ccff5490d44650565e445c4b15e8aff8c
- https://github.com/haproxytech/dataplaneapi/releases/tag/v3.4.4
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.