REDHAT-BUG-2491924: High severity Traefik traefik vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Traefikto a version that resolves this vulnerability.Fixed in 3.7.3
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2491924?
The severity of REDHAT-BUG-2491924 is classified as high with a CVSS score of 7.
How do I fix REDHAT-BUG-2491924?
To address REDHAT-BUG-2491924, upgrade Traefik to version 3.7.3 or later.
What is the impact of REDHAT-BUG-2491924?
REDHAT-BUG-2491924 allows unauthenticated clients to bypass router-specific mTLS enforcement when HTTP/3 is enabled.
When was REDHAT-BUG-2491924 published?
REDHAT-BUG-2491924 was published on June 23, 2026.
What product is affected by REDHAT-BUG-2491924?
The affected product is Traefik, specifically prior to version 3.7.3.