All vulnerabilities

Servers and applications

GHSA-j994-9gqj-9hwq

Same-host Ingress TLS option conflict disables client-certificate authentication

Severity
High 8.2
Published
21 Aug 2026
Last changed
21 Aug 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.7.11
Weakness
Improper authentication (CWE-287)Improper certificate validation (CWE-295)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read data
CVSS vector
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
Sources
Project advisories (GitHub)

Description

There is a high severity vulnerability in Traefik's 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, so two Ingress objects sharing the same host, the same client CA secret and the same client-authentication mode produced two distinct TLS options for that host name. Traefik treats that 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 one. The generated option name is now derived from the client CA secret and the client-authentication mode alone, so Ingresses expressing the same mTLS policy resolve to a single TLS option.

From traefik/traefik's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
TraefikServers and applications · github:traefik/traefik
  • From 3.7.0 before 3.7.11

About Traefik

HTTP reverse proxy and load balancer

From Wikidata, CC0 1.0.
Docker Hub pulls
3,604,536,669Docker Hub, 15 Nov 2026
GitHub stars
65,551GitHub, 15 Nov 2026
Forks
6,312GitHub, 15 Nov 2026
Latest release
v3.7.19GitHub, 15 Nov 2026
Released
13 Nov 2026GitHub
License
Expat licenseWikidata
Written in
GoWikidata
First published on GitHub
13 Sept 2015GitHub

Release lines

ReleaseLatestSecurity fixes
3.73.7.19Yes
3.63.6.25Ended 16 Aug 2026
3.53.5.6Ended 7 Nov 2025
3.43.4.5Ended 23 Jul 2025
3.33.3.7Ended 5 May 2025
3.23.2.5Ended 6 Jan 2025

From endoflife.date.

References