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

Authentication Bypass in github.com/traefik/traefik/v3 (CVE-2026-88007)

Summary

Authentication bypass in github.com/traefik/traefik/v3 (CVE-2026-88007). Confidential information can be exposed externally. Exploitable via ConnContext. Mitigation: upgrade to 3.7.13 or later.

Original description

The description as published by the source.

Summary

Traefik's HTTP/3 request path did not initialize the connection-scoped backend transport holder that isolates connection-bound NTLM and Negotiate (Kerberos) authentication on the HTTP/1.1 and HTTP/2 paths. The HTTP/3 entrypoint reuses the HTTPS handler chain and reaches the same backend round-tripper, but its ConnContext never called service.AddTransportOnContext, so kerberosRoundTripper fell back to the shared backend transport instead of a per-frontend-connection pool. On a route served over HTTP/3 to a backend that binds identity to a persistent connection via NTLM or Negotiate, an unrelated HTTP/3 client could be assigned a backend connection already authenticated as a victim and inherit that identity, reading victim-only data and performing actions as the victim without presenting the victim's credentials. Affected deployments require HTTP/3 enabled on the entrypoint, a backend using connection-bound NTLM/Negotiate authentication, and backend keep-alive; deployments using ordinary per-request authentication are not affected.

Patches

For more information

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

Original Description

Traefik HTTP/3 Backend NTLM Connection Reuse

Summary

Traefik's HTTP/3 request path does not initialize the connection-scope…

Source: NIST National Vulnerability Database 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-88007 has been found in github.com/traefik/traefik/v3.
Attackers can target a specific entry point like ConnContext 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/v3 to 3.7.13 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik/v3 CVE-2026-88007" on the vendor's site.

CVE-2026-88007 (github.com/traefik/traefik/v3) — CWE-287 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ConnContext / service.AddTransportOnContext / kerberosRoundTripper / f2d0794417e4d06343e6e7c4722143f5b34bee45
Patched: 3.7.13 — 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

Authentication bypass (CWE-287) exists in github.com/traefik/traefik/v3. Attackers reach the vulnerable code path via ConnContext without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/traefik/traefik/v3. Attack surface: ConnContext / service.AddTransportOnContext / kerberosRoundTripper / f2d0794417e4d06343e6e7c4722143f5b34bee45.

🔥 Severity

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

🔧 How to fix

Update to 3.7.13.

🛡️ 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

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. 2
    Apply patch patch 
    Upgrade github.com/traefik/traefik/v3 to 3.7.13

    ステージング環境で 3.7.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

go github.com/traefik/traefik/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.13"}]}]
go github.com/traefik/traefik/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.57"}]}]

References

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