high CVSS 8.1 EPSS 0.48%

CVE-2026-71327·Traefik vulnerability

Traefik is an open source HTTP reverse proxy and load balancer. From 3.0.0 until 3.6.25 and 3.7.10, Traefik's Kubernetes Gateway API provider in pkg/provider/kubernetes/gateway/httproute.go, grpcroute.go, tcproute.go, and tlsroute.go builds HTTPRoute, GRPCRoute, TCPRoute, and TLSRoute router and service identities by hyphen-concatenating namespace, route name, Gateway identity, entry point, and rule index, allowing colliding Routes to overwrite another namespace's backend. This issue is fixed in 3.6.25 and 3.7.10.

Severity
high
Software
Traefik
Fixed in
3.7.10
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.48% — higher than 40% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-71327 scores 8.1 on CVSS, so a successful attack would be serious — but at 0.48%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

From: 3.7.0

Until: 3.7.10

Fixed in: 3.7.10

How to fix this CVE

Update Traefik immediately to version 3.7.10 or later to patch the route identity collision vulnerability in the Kubernetes Gateway API provider. This vulnerability allows attackers with access to create routes in one namespace to overwrite backend configurations belonging to other namespaces, potentially redirecting traffic or exposing sensitive services. Apply the patch during your next maintenance window to prevent cross-namespace route hijacking.

sudo dnf update traefik --refresh

Defensia detects this vulnerability

How to check if you are affected

  1. Run `traefik --version` or check `/usr/bin/traefik --version` to identify the installed Traefik version on the system.
  2. Execute `kubectl get gatewayclass,gateway,httproute,grpcroute,tcproute,tlsroute --all-namespaces` to confirm if the Kubernetes Gateway API provider is actively configured.
  3. Search container logs with: `docker logs <container_id> 2>&1 | grep -iE '(gateway|route|collision|identity)' | tail -20` to detect any anomalies related to route processing.
  4. Verify the fix by running `traefik --version` post-update and confirming the version is 3.7.10 or later, then validate Gateway API routes are functioning correctly with `kubectl describe httproute -A`.

FAQ

What is CVE-2026-71327?

This vulnerability in Traefik's Kubernetes Gateway API provider allows route identity collisions where malicious routes in one namespace can overwrite backend service identities of routes in other namespaces. Attackers with namespace-level route creation permissions can exploit this to redirect traffic or expose backend services they should not access.

Is CVE-2026-71327 being actively exploited?

No, CVE-2026-71327 is not currently listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available, but the vulnerability remains critical for multi-tenant Kubernetes deployments.

What versions of Traefik are affected by CVE-2026-71327?

Traefik versions 3.7.0 through 3.7.9 are vulnerable. Additionally, versions 3.0.0 through 3.6.24 are affected. The vulnerability is fixed in Traefik 3.7.10 and 3.6.25.

How do I check if my server is vulnerable to CVE-2026-71327?

Run `traefik --version` and check if the version falls between 3.7.0-3.7.9 or 3.0.0-3.6.24. If Kubernetes Gateway API provider is enabled (check Traefik configuration or logs for 'gateway' provider mentions), your deployment is vulnerable until patched.

Does Defensia detect CVE-2026-71327?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Traefik is installed on a monitored server, CVE-2026-71327 will appear in your dashboard with remediation steps.

Related Traefik CVEs

CVE-2026-53622CVSS 10Traefik 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.
CVE-2026-48491CVSS 10Traefik is an HTTP reverse proxy and load balancer. From 3.7.0 until 3.7.3, there is a high severity vulnerability in Traefik's domain-fronting protection (SNICheck) that allows an unauthenticated client to bypass mutual TLS enforced through wildcard router TLSOptions. When a router uses a wildcard host rule such as Host(*.example.com) with stricter TLS options (for example RequireAndVerifyClientCert), SNICheck resolves the TLS options for the HTTP Host header using exact map lookups only and never applies wildcard matching. If another permissive SNI is served on the same entrypoint, an attacker can complete the TLS handshake under the permissive options and then send an HTTP Host header targeting the wildcard-protected backend, reaching it without presenting a client certificate. This affects the regular HTTPS / HTTP-2 path and does not require HTTP/3. This vulnerability is fixed in 3.7.3.
CVE-2026-48020CVSS 10Traefik is an HTTP reverse proxy and load balancer. Prior to 2.11.48, 3.6.19, and 3.7.3, there is a high severity vulnerability in Traefik's StripPrefix middleware that allows an unauthenticated attacker to bypass route-level authentication and authorization. When a public router matches on a PathPrefix rule and applies the StripPrefix middleware, a request path containing .. or its percent-encoded form %2e%2e can match the public route at routing time and then, after the prefix is stripped and the path is normalized, resolve to a path served by a separate, authenticated router. As a result, an attacker can reach protected backend paths — such as admin or internal configuration endpoints — without satisfying the authentication middleware attached to the protected router. This vulnerability is fixed in 2.11.48, 3.6.19, and 3.7.3.
CVE-2026-54763CVSS 10Traefik is an HTTP reverse proxy and load balancer. Prior to v2.11.51, v3.6.22, and v3.7.6, Traefik's BasicAuth, DigestAuth, and ForwardAuth middlewares strip canonical-cased spoofed identity headers before writing Traefik's own value, but do not account for underscore-variant header names, which many backends normalize identically to dashed forms. An attacker able to reach a protected route can inject an underscore-variant header that survives Traefik's stripping and reaches the backend alongside, or on the unauthenticated ForwardAuth authResponseHeaders path instead of, the value Traefik intended to set, spoofing identity or authorization context. This issue is fixed in versions v2.11.51, v3.6.22, and v3.7.6.
CVE-2026-44774CVSS 9.9Traefik is an HTTP reverse proxy and load balancer. Prior to 2.11.46, 3.6.17, and 3.7.1, Traefik's Kubernetes Gateway API provider allows a tenant with HTTPRoute creation permissions to expose the REST provider handler, bypassing the providers.rest.insecure=false setting. The Gateway provider accepts any TraefikService backend reference whose name ends with @internal, making it possible to route traffic to rest@internal in addition to the intended api@internal. In shared Gateway deployments where the REST provider is enabled, this allows a low-privileged actor to gain live dynamic configuration write access to Traefik, enabling unauthorized reconfiguration of routers and services. This vulnerability is fixed in 2.11.46, 3.6.17, and 3.7.1.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-71327. Free for 1 server.

Get started free