Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71327 high CVSS 8.1

Vulnerability in github.com/traefik/traefik/v3 (CVE-2026-71327)

Summary

Vulnerability in github.com/traefik/traefik/v3 (CVE-2026-71327). Confidential information can be exposed externally. Exploitable via Authorization header. Mitigation: upgrade to 3.7.10 or later.

Original description

The description as published by the source.

Summary

There is a high severity vulnerability in Traefik's Kubernetes Gateway API provider. Router and service identities for HTTPRoute, GRPCRoute, TCPRoute and TLSRoute objects were built by hyphen-concatenating the route namespace, the route name, the Gateway identity, the entry point and the rule index, a construction that is not injective because Kubernetes names may themselves contain hyphens. Two distinct Routes attached to the same Gateway with equivalent match rules can therefore produce the same identity, and the Route loaded later silently overwrites the earlier one, so a tenant able to create an accepted Route in a colliding namespace/name combination can redirect another namespace's traffic to a backend it controls. All Traefik v3 minor lines are affected; the lines older than v3.6 are no longer maintained and will not receive a patch of their own, so users running them should upgrade to a maintained, patched release.

Patches

For more information

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

Original Description

Summary

Traefik's Kubernetes Gateway provider constructs internal HTTPRoute and
GRPCRoute identities by concatenating namespace, route name, Gateway identity,
entrypoint, and rule index with hyphens. Kubernetes names may themselves
con…

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-71327 has been found in github.com/traefik/traefik/v3.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/traefik/traefik/v3 to 3.7.10 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik/v3 CVE-2026-71327" on the vendor's site.

CVE-2026-71327 (github.com/traefik/traefik/v3) — CWE-694 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Authorization header / HTTPRoute / GRPCRoute / TCPRoute
Patched: 3.7.10 — 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-694) exists in github.com/traefik/traefik/v3. Attackers reach the vulnerable code path via Authorization header.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/traefik/traefik/v3. Attack surface: Authorization header / HTTPRoute / GRPCRoute / TCPRoute.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.7.10.

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

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

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

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

Affected packages

go github.com/traefik/traefik/v3
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.10"}]}]
Go github.com/traefik/traefik
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/traefik/traefik/v2
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

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