# CVE-2026-85596: Traefik v3.7 Authentication Bypass via TLS Option Conflict

> Attackers can bypass client certificate authentication in Traefik Kubernetes Ingress NGINX provider by triggering a TLS option conflict.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-j994-9gqj-9hwq, GHSA-rgpg-cpwg-4f45, MINI-4h69-mw5j-fwr5, MINI-gp8c-vx46-fcqq

## What is CVE-2026-85596?

CVE-2026-85596 is a high-severity authentication bypass vulnerability in Traefik Traefik, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Traefik versions >= v3.7.0 and <= v3.7.10 contain an authentication bypass in the Kubernetes Ingress NGINX provider. The TLS option generated for an Ingress carrying the nginx.ingress.kubernetes.io/auth-tls-secret annotation was named after the Ingress namespace and name. As a result, two Ingress objects sharing the same host, the same client CA secret, and the same client-authentication mode produced two distinct TLS option names for that host. Traefik treats this as a TLS options conflict and falls back to the entry point's default TLS configuration, which does not request a client certificate, so a route configured with nginx.ingress.kubernetes.io/auth-tls-verify-client: "on" becomes reachable without a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Traefik Traefik.

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

Upgrade to a fixed version.

## Is CVE-2026-85596 being exploited?

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

## Other vulnerabilities in Traefik Traefik

- [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8)
- [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3)
- [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3)
- [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1)
- [CVE-2026-88009](https://insights.sbomify.com/CVE-2026-88009/): Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85596 is a high-severity authentication bypass vulnerability in Traefik Traefik, published on 4 Sep 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-85596 in the wild and no public exploit code.

Affected product: Traefik Traefik. 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-85596/ (Markdown: https://insights.sbomify.com/CVE-2026-85596/index.md)
```

## Sources

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

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