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.
Severity
CVSS 3.1
9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4%(unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-306Missing Authentication for Critical Functionality
Show the promptExplain CVE-2026-109575 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109575?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109575?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109575 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
haproxy:data plane api ce
haproxy:data plane api ee
Versions
From the CNA's record in the CVE List.
Product
Affected
HAProxy Data Plane API EE
from 2.2.0-ee1 through 2.9.28-ee1
HAProxy Data Plane API EE
from 3.0-ee through 3.0.24-ee1
HAProxy Data Plane API EE
from 3.1-ee through 3.2.16-ee1
HAProxy Data Plane API EE
from 3.3-ee through 3.3.8-ee1
HAProxy Data Plane API EE
from 3.4-ee through 3.4.3-ee2
HAProxy Data Plane API CE
from 2.2.0 through 2.9.28
HAProxy Data Plane API CE
from 3.0.0 through 3.0.24
HAProxy Data Plane API CE
from 3.1.0 through 3.2.16
HAProxy Data Plane API CE
from 3.3.0 through 3.3.8
HAProxy Data Plane API CE
from 3.4.0 through 3.4.3
Fixed in
Product
Fixed in
HAProxy Data Plane API EE
2.9.29-ee1
HAProxy Data Plane API EE
3.0.25-ee1
HAProxy Data Plane API EE
3.2.17-ee1
HAProxy Data Plane API EE
3.3.9-ee1
HAProxy Data Plane API EE
3.4.4-ee1
HAProxy Data Plane API CE
2.9.29
HAProxy Data Plane API CE
3.0.25
HAProxy Data Plane API CE
3.2.17
HAProxy Data Plane API CE
3.3.9
HAProxy Data Plane API CE
3.4.4
Attack patterns (CAPEC)
CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
CAPEC-166 Force the System to Reset Values Severity: Medium