# CVE-2026-109575: Auth bypass in Data Plane API CE

> Unauthenticated attackers can bypass authentication on HTTP or UNIX listeners to gain full administrative access and modify HAProxy configurations when TLS CA is configured.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-7jqw-rhp8-c8vf

## What is CVE-2026-109575?

CVE-2026-109575 is a critical authentication bypass vulnerability in HAProxy Data Plane API CE, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-109575?


## How do I fix CVE-2026-109575?

No fix has been published for CVE-2026-109575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109575 being exploited?

There is no known exploitation of CVE-2026-109575 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109575 and fix it if it is affected.

What it is: CVE-2026-109575 is a critical authentication bypass vulnerability in HAProxy Data Plane API CE, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109575 in the wild and no public exploit code.

Affected product: HAProxy Data Plane API CE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109575/ (Markdown: https://insights.sbomify.com/CVE-2026-109575/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109575
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109575
- OSV: https://osv.dev/vulnerability/CVE-2026-109575

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109575/
Summaries are generated and may contain mistakes; the official description above is the record.