Vulnerabilities / CVE-2026-85596

critical

CVE-2026-85596

github.com/traefik/traefik: Traefik: Authentication bypass due to TLS configuration conflict

Published Modified CWE 287
In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Red Hat7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by Red Hat (high).

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.

Affected packages and fixed versions

SourcePackageFixed in
minimostraefik-3, traefik-fips-33.7.11-r0
rapidfort alpine 3.20traefik3.7.11-r0
rapidfort alpine 3.21traefik3.7.11-r0
rapidfort alpine 3.22traefik3.7.11-r0
rapidfort alpine 3.23traefik3.7.11-r0
rapidfort alpine 3.24traefik3.7.11-r0
Show all 7 entries from 6 sources
SourcePackageFixed in
minimostraefik-33.7.11-r0
minimostraefik-fips-33.7.11-r0
rapidfort alpine 3.20traefik3.7.11-r0
rapidfort alpine 3.21traefik3.7.11-r0
rapidfort alpine 3.22traefik3.7.11-r0
rapidfort alpine 3.23traefik3.7.11-r0
rapidfort alpine 3.24traefik3.7.11-r0

References

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.