Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71324 critical CVSS 9.1

Vulnerability in github.com/traefik/traefik/v2 (CVE-2026-71324)

Summary

Vulnerability in github.com/traefik/traefik/v2 (CVE-2026-71324). Confidential information can be exposed externally. Exploitable via GET /delay/2. Mitigation: upgrade to 2.11.53 or later.

Original description

The description as published by the source.

Summary

There is a critical vulnerability in Traefik's default HTTP reverse proxy that leads to unauthenticated cross-user response poisoning. When a client opens an HTTP/2 or HTTP/3 CONNECT request, Traefik forwards it — body included — to an HTTP/1.1 upstream over a shared net/http.Transport. If the upstream answers the CONNECT with a keep-alive non-2xx response without draining the body, the now-desynchronized backend socket is returned to Traefik's shared connection pool and reused for other clients, letting an attacker make a different client read a response the attacker smuggled — which may be another user's authenticated or private content. The entrypoint's sanitizePath option (default true) is not a reliable defense: backends that answer CONNECT / with a keep-alive non-2xx remain exploitable. The experimental FastProxy implementation was not affected. The issue is fixed by deferring the forwarded CONNECT payload until the backend accepts the tunnel, by not returning CONNECT connections to the shared idle pool, and by discarding the CONNECT body in the ForwardAuth path.

Patches

For more information

If you have any questions or comments about this advisory, please open an issue.

Original Description

Summary

Traefik's default…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-71324 has been found in github.com/traefik/traefik/v2.
Attackers can target a specific entry point like GET /delay/2 over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade github.com/traefik/traefik/v2 to 2.11.53 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik/v2 CVE-2026-71324" on the vendor's site.

CVE-2026-71324 (github.com/traefik/traefik/v2) — CWE-444 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /delay/2 / GET /get / CONNECT / sanitizePath
Patched: 2.11.53 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-444) exists in github.com/traefik/traefik/v2. Attackers reach the vulnerable code path via GET /delay/2 without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/traefik/traefik/v2. Attack surface: GET /delay/2 / GET /get / CONNECT / sanitizePath.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.11.53.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /delay/2 requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/traefik/traefik/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/traefik/traefik/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/traefik/traefik/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /delay/2' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /delay/2 への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/traefik/traefik/v2 to 2.11.53

    ステージング環境で 2.11.53 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /delay/2 on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/traefik/traefik/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.11.53"}]}]
go github.com/traefik/traefik/v3
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.9"}]}]
go github.com/traefik/traefik
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.7.34"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details