← Back
CVE-2026-54764
medium
CVSS 5.8
Vulnerability in github.com/traefik/traefik/v2 (CVE-2026-54764)
Summary
vulnerability in github.com/traefik/traefik/v2 (CVE-2026-54764). Risk of unauthorized operations or information disclosure. Exploitable via ``req.TLS``. Mitigation: upgrade to `2.11.51` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54764** has been found in github.com/traefik/traefik/v2.
Attackers can target a specific entry point like ``req.TLS`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade github.com/traefik/traefik/v2 to **2.11.51** or later.
If unsure, ask your IT team or search "github.com/traefik/traefik/v2 CVE-2026-54764" on the vendor's site.
CVE-2026-54764 (github.com/traefik/traefik/v2) — CWE-345 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `req.TLS` / `req` / `forwardReq`
Patched: `2.11.51` — 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-345) exists in github.com/traefik/traefik/v2. Attackers reach the vulnerable code path via ``req.TLS`` without authentication.
📍 Affected scope
github.com/traefik/traefik/v2 — . Attack surface: `req.TLS` / `req` / `forwardReq`.
🔥 Severity
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.11.51**.
🛡️ 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 request patterns matching this CVE's known IOCs. 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/traefik/traefik/v2 to 2.11.51ステージング環境で 2.11.51 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/traefik/traefik/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.51"}]}]
go
github.com/traefik/traefik/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.6"}]}]
go
github.com/traefik/traefik
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- web https://github.com/traefik/traefik/commit/7ae92d8c2c10ac04ef5a03df0ed5019ce0f44b2d
- web https://github.com/traefik/traefik/pull/13344
- web https://github.com/traefik/traefik/security/advisories/GHSA-3q9r-p662-5j8m
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54764
- web https://github.com/traefik/traefik/releases/tag/v2.11.51
- web https://github.com/traefik/traefik/releases/tag/v3.6.22
- web https://github.com/traefik/traefik/releases/tag/v3.7.6
- web https://github.com/advisories/GHSA-3q9r-p662-5j8m