medium CVSS 5.9 EPSS 0.28%

CVE-2026-119574·Traefik vulnerability

Traefik from 3.2.0 before 3.7.15 contains a data race in the experimental FastProxy that allows unauthenticated attackers to crash the process by abusing HTTP/1 protocol upgrades. Attackers can repeatedly open and abort upgraded connections such as WebSocket, corrupting the unsynchronized shared bufio.Reader and triggering an unrecovered panic that terminates Traefik.

Severity
medium
Software
Traefik
Fixed in
3.7.15
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.28% — higher than 21% 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.

Affected versions

From: 3.2.0

Until: 3.7.15

Fixed in: 3.7.15

How to fix this CVE

Upgrade Traefik to version 3.7.15 or later to resolve a concurrency vulnerability in the experimental FastProxy module that could allow denial-of-service attacks. Organizations running Traefik 3.2.0 through 3.7.14 with HTTP/1 protocol upgrade support enabled should prioritize this update, particularly if WebSocket or similar upgrade mechanisms are in use. Apply the patch during a maintenance window and verify the upgraded version is running before resuming production traffic.

sudo dnf update traefik

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

Repeated HTTP connection attempts with Upgrade headers (e.g., 'Connection: Upgrade', 'Upgrade: websocket') followed by immediate connection aborts, correlating with Traefik panic logs containing 'bufio: invalid use of (*Reader).Peek' or 'bufio: reader used after Close'

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

Implement rate limiting on HTTP Upgrade requests to the same source IP, and enforce connection state validation. Block sequences of rapid Upgrade header submissions from single clients. However, this is a concurrency bug not a web application flaw—patching Traefik itself is the primary remediation.

How to check if you are affected

  1. Step 1: Check installed Traefik version with: traefik version or docker inspect {container_id} | grep -i version (if containerized)
  2. Step 2: Verify if FastProxy is enabled in your Traefik configuration by checking for 'experimental.fastproxy: true' in static config
  3. Step 3: Search Traefik logs for panic messages and goroutine stack traces containing 'bufio.Reader' or 'fastproxy' near unexpected connection terminations
  4. Step 4: After upgrading, run traefik version and confirm the version is 3.7.15 or newer, then perform a connection upgrade test (e.g., WebSocket handshake) to ensure stability

FAQ

What is CVE-2026-119574?

This vulnerability is a data race condition in Traefik's experimental FastProxy component that occurs when handling HTTP/1 protocol upgrades (such as WebSocket connections). An attacker can trigger repeated upgrade attempts to corrupt the internal buffer reader state, causing Traefik to crash with an unrecovered panic.

Is CVE-2026-119574 being actively exploited?

No, this CVE is not currently listed in CISA's Known Exploited Vulnerabilities catalog and no public exploit code is available. However, the attack method is straightforward and does not require authentication, so proactive patching is still recommended.

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

Traefik versions 3.2.0 through 3.7.14 are affected. The vulnerability was introduced in version 3.2.0 and fixed in version 3.7.15.

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

Run 'traefik version' and check if your version falls between 3.2.0 and 3.7.14 inclusive. Then verify if the experimental FastProxy is enabled in your static configuration file by looking for 'experimental.fastproxy: true'.

Does Defensia detect CVE-2026-119574?

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

Related Traefik CVEs

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-39858CVSS 10Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a high severity authentication bypass vulnerability in Traefik's ForwardAuth and snippet-based authentication middleware. Traefik's forwarded-header sanitization logic targets only canonical header names (e.g., X-Forwarded-Proto) and does not strip or normalize alias variants that use underscores instead of dashes (e.g., X_Forwarded_Proto). These unsanitized alias headers are forwarded intact to the authentication backend. When the backend normalizes underscore and dash header forms equivalently, an attacker can inject spoofed trust context — such as a trusted scheme or host — through the alias headers and bypass authentication on protected routes without valid credentials. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
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-35051CVSS 10Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an authentication bypass vulnerability in Traefik's ForwardAuth middleware when trustForwardHeader=false is configured and Traefik is deployed behind a trusted upstream proxy. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
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.

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-119574. Free for 1 server.

Get started free