Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.8

CVE-2026-53622: Traefik: Unauthenticated access to mTLS-protected services via HTTP/3

GHSA-9cr8-q42q-g8m7 CVE-2026-53622 GHSA-9cr8-q42q-g8m7 CVE-2026-53622
Summary

A critical vulnerability in Traefik's HTTP/3 configuration can allow unauthenticated clients to access services protected by client certificate authentication. This is possible when HTTP/3 is enabled and a client connects to a Traefik entrypoint using a hostname that doesn't match the expected case or contains a wildcard. To fix this, update to Traefik version 3.7.3 or later.

What to do
  • Update traefik to version 3.7.3.
Affected software
Ecosystem VendorProductAffected versions
go traefik <= 3.7.2
Fix: upgrade to 3.7.3
go github.com traefik <= 2.11.50
go github.com traefik <= 1.7.34
Go traefik < 3.7.3
Fix: upgrade to 3.7.3
Go traefik github.com/traefik/traefik/v2 <= 2.11.50
Go traefik github.com/traefik/traefik <= 1.7.34
traefik traefik < 3.7.3
cpe:2.3:a:traefik:traefik:*:*:*:*:*:*:*:*
Original title
Traefik is an HTTP reverse proxy and load balancer. Prior to 3.7.3, there is a critical vulnerability in Traefik's HTTP/3 (QUIC) TLS configuration selection that allows unauthenticated clients to b...
Original description
Traefik is an HTTP reverse proxy and load balancer. Prior to 3.7.3, there is 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 3.7.3.
ghsa CVSS4.0 7.8
Vulnerability type
CWE-288 Authentication Bypass Using Alternate Path
CWE-289
Published: 23 Jun 2026 · Updated: 20 Jul 2026 · First seen: 16 Jun 2026