Is CVE-2026-71324 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-71324 being exploited in the wild.

How severe is CVE-2026-71324?

High severity, with a CVSS score of 4, published 6 August 2026.

Which products and versions are affected?

github.com/traefik/traefik (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.7.34; github.com/traefik/traefik/v2 (Go) SEMVER:introduced=0,fixed=2.11.53; github.com/traefik/traefik/v3 (Go) SEMVER:introduced=0,fixed=3.6.24, SEMVER:introduced=0,fixed=3.6.24,introduced=3.7.0,fixed=3.7.9; Traefik Labs Traefik Proxy = 3.7.0, <= 3.7.8.

Is there a fix for CVE-2026-71324?

Yes. github.com/traefik/traefik/v2 (Go): upgrade to 2.11.53 or later; github.com/traefik/traefik/v3 (Go): upgrade to 3.6.24, 3.7.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-71324 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-71324?

Check whether you run github.com/traefik/traefik (Go), github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-71324: Traefik response poisoning via proxied CONNECT in shared connection pool

Q: Is there a fix for CVE-2026-71324?

Yes. github.com/traefik/traefik/v2 (Go): upgrade to 2.11.53 or later; github.com/traefik/traefik/v3 (Go): upgrade to 3.6.24, 3.7.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-71324 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-71324?

Check whether you run github.com/traefik/traefik (Go), github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-71324 · Severity: high · CVSS 4 · Published 2026-08-06

A vulnerability in Traefik's reverse proxy allows an attacker to perform response poisoning, where one user may receive the web response intended for another user. This occurs when Traefik incorrectly reuses backend connections after certain types of network requests. This could lead to the exposure of private user data, session tokens, or other sensitive information to unauthorized parties.

Technologies: github.com/traefik/traefik (Go), github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go), Traefik Labs Traefik Proxy. Vendors: Go, Traefik Labs.

Quick answers

Is CVE-2026-71324 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-71324 being exploited in the wild.
How severe is CVE-2026-71324?: High severity, with a CVSS score of 4, published 6 August 2026.
Which products and versions are affected?: github.com/traefik/traefik (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.7.34; github.com/traefik/traefik/v2 (Go) SEMVER:introduced=0,fixed=2.11.53; github.com/traefik/traefik/v3 (Go) SEMVER:introduced=0,fixed=3.6.24, SEMVER:introduced=0,fixed=3.6.24,introduced=3.7.0,fixed=3.7.9; Traefik Labs Traefik Proxy <= 1.7.34, <= 2.11.52, <= 3.6.23, >= 3.7.0, <= 3.7.8.
Is there a fix for CVE-2026-71324?: Yes. github.com/traefik/traefik/v2 (Go): upgrade to 2.11.53 or later; github.com/traefik/traefik/v3 (Go): upgrade to 3.6.24, 3.7.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-71324 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-71324?: Check whether you run github.com/traefik/traefik (Go), github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/traefik/traefik/v2 (Go): upgrade to 2.11.53 or later
```
go get github.com/traefik/traefik/v2@v2.11.53
```
github.com/traefik/traefik/v3 (Go): upgrade to 3.6.24, 3.7.9 or later
```
go get github.com/traefik/traefik/v3@v3.7.9
```

Technical details

Traefik's default reverse proxy (using net/http/httputil) forwards HTTP/2 or HTTP/3 CONNECT requests to HTTP/1.1 upstreams without framing the body. If the upstream responds with a keep-alive non-2xx status without draining the body, the backend socket becomes desynchronized. This socket is then returned to Traefik's shared connection pool. When a subsequent client reuses this socket, they may receive a response smuggled by the previous attacker or a response intended for a different user. The vulnerability also affects the ForwardAuth middleware when configured to forward request bodies. Patches are available in versions 2.11.53, 3.6.24, and 3.7.9.

Affected products

traefik traefik <= 1.7.34, <= 2.11.52, <= 3.6.23, >= 3.7.0, <= 3.7.8

Identifiers

CVE-2026-71324
GHSA-3ccp-42pg-hgv6
GO-2026-6201

Timeline

2026-07-27: disclosed
2026-08-06: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.