← Back
CVE-2026-54761
high
CVSS 7.1
Vulnerability in github.com/traefik/traefik/v3 (CVE-2026-54761)
Summary
vulnerability in github.com/traefik/traefik/v3 (CVE-2026-54761). Confidential information can be exposed externally. Exploitable via ``crossProviderNamespaces``. Mitigation: upgrade to `3.7.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54761** has been found in github.com/traefik/traefik/v3.
Attackers can target a specific entry point like ``crossProviderNamespaces`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade github.com/traefik/traefik/v3 to **3.7.5** or later.
If unsure, ask your IT team or search "github.com/traefik/traefik/v3 CVE-2026-54761" on the vendor's site.
CVE-2026-54761 (github.com/traefik/traefik/v3) — CWE-284 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `crossProviderNamespaces` / `HTTPRoute` / `backendRef.namespace` / `TraefikService`
Patched: `3.7.5` — 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-284) exists in github.com/traefik/traefik/v3. Attackers reach the vulnerable code path via ``crossProviderNamespaces`` without authentication.
📍 Affected scope
github.com/traefik/traefik/v3 — . Attack surface: `crossProviderNamespaces` / `HTTPRoute` / `backendRef.namespace` / `TraefikService`.
🔥 Severity
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **3.7.5**.
🛡️ 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/v3' .` 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/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/traefik/traefik/v3` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/traefik/traefik/v3 to 3.7.5ステージング環境で 3.7.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/traefik/traefik/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.5"}]}]
go
github.com/traefik/traefik/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go
github.com/traefik/traefik
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- exploit [email protected]
- patch [email protected]
- patch [email protected]
- web https://github.com/advisories/GHSA-3g6v-2r68-prfc