Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-67309 high CVSS 7.5

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

Summary

Path traversal in github.com/traefik/traefik/v3 (CVE-2026-67309). Confidential information can be exposed externally. Exploitable via RewriteTarget. Mitigation: upgrade to 3.7.8 or later.

Original description

The description as published by the source.

Summary

There is a high severity vulnerability in Traefik's Kubernetes Ingress NGINX provider. When an Ingress uses the nginx.ingress.kubernetes.io/rewrite-target annotation with a regular expression that captures attacker-controlled text without requiring a path separator (for example path /api(.*) with rewrite target /$1), the generated RewriteTarget middleware can turn an initially safe request path into a dot-segment traversal path after the router has already been selected.

Patches

For more information

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

Original Description

Summary

Traefik's Kubernetes Ingress NGINX provider creates an internal RewriteTarget middleware for the nginx.ingress.kubernetes.io/rewrite-target annotation. When an Ingress path captures attacker-controlled text without requiring a path separator, the middleware can turn an initially safe path into a dot-segment traversal path after Traefik has already selected the router.

For example, with Ingress path /api(.*) and rewrite target /$1, an unauthenticated request to /api../admin follows this flow:

  1. The default entry-point path sanitizer leaves /api../admin unchanged because api.. is one ordinary segment.
  2. The public router's PathRegexp("(?i)^/api(.*)") rule matches.
  3. RewriteTarget captures ../admin and creates `/../…

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

CVE-2026-67309 (github.com/traefik/traefik/v3) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: RewriteTarget / api.. / ReplacePathRegex / master
Patched: 3.7.8 — 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. Attackers reach the vulnerable code path via RewriteTarget without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/traefik/traefik/v3. Attack surface: RewriteTarget / api.. / ReplacePathRegex / master.

🔥 Severity

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

🔧 How to fix

Update to 3.7.8.

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

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

  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.8"}]}]
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