Skip to content
Fencer Intel
critical 9.1

CVE-2026-71324 json

Traefik: Cross-user response poisoning via proxied CONNECT on Traefik's shared backend keep-alive pool

published 3mo ago modified last mo. also EUVD-2026-54288 , GHSA-3ccp-42pg-hgv6 , GO-2026-6201

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.53, 3.6.24, and 3.7.9, Traefik's default HTTP reverse proxy forwards a plain HTTP/2 or HTTP/3 CONNECT request and its body to an HTTP/1.1 upstream through a shared net/http.Transport. When the upstream answers the CONNECT with a keep-alive non-2xx response and does not drain the body, Traefik returns the desynchronized backend socket to its shared pool and reuses it for other clients. An unauthenticated attacker can use this behavior to make a different client read the attacker's smuggled response, which can include authenticated or private content from another request. The ForwardAuth middleware with forwardBody true and preserveRequestMethod true can re-issue a CONNECT with the buffered body attached, exposing the auth-client pool to the same desynchronization. This issue is fixed in 2.11.53, 3.6.24, and 3.7.9.

Patch / fix

  • go github.com/traefik/traefik/v2 2.11.53
  • go github.com/traefik/traefik/v3 3.6.24, 3.7.9
  • traefik traefik 2.11.53, 3.6.24, 3.7.9
  • govulncheck-vulndb SLES for SAP applications 16.0, SLES 16.0 0.0.20260827T195228-160000.1.1

suse advisories SUSE-SU-2026:23625-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260827T195228-160000.1.1

opensuse advisories openSUSE-SU-2026:21761-1

Is CVE-2026-71324 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-71324 updated cvss 8.6

github.com/traefik/traefik: Traefik: Information disclosure via response poisoning in shared backend pool

  • Red Hat OpenShift Dev Spaces 3.31 devspaces/traefik-rhel9 1792464177
    fixed: vendor fix RHSA-2026:90321
  • Red Hat OpenShift Dev Spaces 3.31 devspaces/udi-rhel9 1792708612, devspaces/code-rhel9 1792599388, devspaces/server-rhel9 1792775639, devspaces/openvsx-rhel9 1792494821, devspaces/udi-base-rhel9 1792686842, devspaces/code-sshd-rhel9 1792598059, +9 more Red Hat OpenShift GitOps openshift-gitops-1/argo-rollouts-rhel8, openshift-gitops-1/argo-rollouts-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3mo ago

Exploit prediction

1.06% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 4.0 7.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
CNA 4.0 7.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/traefik/traefik/v2
<2.11.53
2.11.53
go github.com/traefik/traefik/v3
<3.6.24
>=3.7.0, <3.7.9
3.6.24
3.7.9
go github.com/traefik/traefik
<=1.7.34
all versions
 no fix listed

Affected products

  • traefik traefik

Classification

Weakness
  • CWE-444 Inconsistent Interpretation of HTTP Requests

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.