CVE-2026-53622 Traefik: HTTP/3 mTLS bypass via exact SNI TLSOptions lookup for wildcard and mixed-case hosts
Attackers can bypass mTLS enforcement on HTTP/3 routers with wildcard or mixed-case hostnames, accessing protected backends without client certificates.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-53622?
CVE-2026-53622 is a high-severity authentication bypass vulnerability in Traefik Traefik, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Traefik is an HTTP reverse proxy and load balancer. Versions prior to 3.7.3, 3.6.18, and 2.11.51 have a critical vulnerability in Traefik's HTTP/3 (QUIC) TLS configuration selection that allows unauthenticated clients to bypass router-specific mTLS enforcement. When HTTP/3 is enabled on an entrypoint, the TLS handshake selects the applicable TLS configuration through an exact, case-sensitive lookup on the SNI value, which fails to match wildcard host patterns (e.g., *.example.com) or case variants of the configured hostname. Because the handshake falls back to the default TLS configuration — which may not require client certificates — a client can complete the QUIC handshake without presenting a certificate, while the subsequent HTTP routing layer still dispatches the request to a backend protected by a router-specific mTLS policy. The issue affects deployments where HTTP/3 is enabled, a router uses a wildcard Host rule or case-insensitive hostname matching, a router-specific TLSOptions enforces client certificate authentication, and UDP access to the entrypoint is reachable by an attacker. This vulnerability is fixed in versions 3.7.3, 3.6.18, and 2.11.51.
Which versions are affected by CVE-2026-53622?
11 open source packages ship an affected version, including github.com/traefik/traefik/v3, github.com/traefik/traefik and github.com/traefik/traefik/v2. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/traefik/traefik/v3 Go | All versions | 3.6.18 |
github.com/traefik/traefik/v3 Go | All versions | 3.6.18 |
github.com/traefik/traefik/v3 Go | All versions | 3.7.3 |
github.com/traefik/traefik/v3 Go | From 3.7.0 | 3.7.3 |
github.com/traefik/traefik/v3 Go | From 3.7.0 | 3.7.3 |
github.com/traefik/traefik Go | All versions | None |
5 more packages
github.com/traefik/traefik Go | All versions to 1.7.34 | None |
github.com/traefik/traefik Go | All versions to 1.7.34 | None |
github.com/traefik/traefik/v2 Go | All versions | 2.11.51 |
github.com/traefik/traefik/v2 Go | All versions | 2.11.51 |
github.com/traefik/traefik/v2 Go | All versions | 2.11.51 |
Products include Traefik Traefik.
How do I fix CVE-2026-53622?
Upgrade github.com/traefik/traefik/v3 to a fixed version for your release line: 3.6.18 or 3.7.3.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-53622 being exploited?
There is no known exploitation of CVE-2026-53622 in the wild and no public exploit code.
Other vulnerabilities in Traefik Traefik
- CVE-2024-45410 HTTP client can remove the X-Forwarded headers in Traefik
- CVE-2026-88877 Traefik v3.7.0 Authentication Bypass via from-to-www-redirect
- CVE-2026-85595 Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth
- CVE-2026-88007 Traefik HTTP/3 Backend NTLM Connection Reuse
- CVE-2026-88009 Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
Sources
Also known as GHSA-9cr8-q42q-g8m7, GO-2026-5287, MINI-94jf-px4q-g9vw, MINI-r565-x5cx-fjgc, MINI-rg63-2xpq-3p2j.