All vulnerabilities

Servers and applications

GHSA-g55h-rg46-x9c5

TLS option confusion in multi-host routers can bypass mTLS for protected hosts

Severity
High 8.2
Published
21 Aug 2026
Last changed
21 Aug 2026
Added to UpHeron
3 Nov 2026
Fixed in
2.11.55, 3.7.11
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 TLS options conflict resolution. TLS options are applied during the handshake and are therefore mapped to the host names of a router rule rather than to the router itself, so when several routers on the same entry point serve the same host name with different TLS options Traefik arbitrates the conflict by falling back to the default TLS options — and for a multi-host router that fallback is applied to every host name in the rule, including the ones that are not themselves in conflict. A router that requires client-certificate authentication for one of its hosts therefore stops enforcing it as soon as another router creates a TLS option conflict on any other host of the same rule, and a client without a certificate can reach the protected backend.

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

Affected software

SoftwareAffected versions
TraefikServers and applications · github:traefik/traefik
  • Every version before 2.11.55
  • From 3.0.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