Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-40912 high CVSS 8.2

Path Traversal in github.com/traefik/traefik/v3 (CVE-2026-40912)

Summary

path traversal in github.com/traefik/traefik/v3 (CVE-2026-40912). Confidential information can be exposed externally. Mitigation: upgrade to `3.6.14, 3.7.0-rc.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-40912** has been found in github.com/traefik/traefik/v3. Confidential information can be exposed externally. CVSS score: 8.2/10. What to do: upgrade github.com/traefik/traefik/v3 to **3.6.14, 3.7.0-rc.2** or later. If unsure, ask your IT team or search "github.com/traefik/traefik/v3 CVE-2026-40912" on the vendor's site.
CVE-2026-40912 (github.com/traefik/traefik/v3) — CWE-22 / CVSS v3 8.2 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Patched: `3.6.14, 3.7.0-rc.2` — 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
**Path traversal** (CWE-22) exists in github.com/traefik/traefik/v3.
📍 Affected scope
github.com/traefik/traefik/v3 — .
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to **3.6.14, 3.7.0-rc.2**.
🛡️ 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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade github.com/traefik/traefik/v3 to 3.6.14, 3.7.0-rc.2

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

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go github.com/traefik/traefik/v3
[{"type":"SEMVER","events":[{"introduced":"3.0.0-beta1"},{"fixed":"3.6.14"},{"introduced":"3.7.0-ea.1"},{"fixed":"3.7.0-rc.2"}]}]
go github.com/traefik/traefik/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.11.43"}]}]
go github.com/traefik/traefik
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →