Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54764 medium CVSS 5.8

Vulnerability in github.com/traefik/traefik/v2 (CVE-2026-54764)

Summary

Vulnerability in github.com/traefik/traefik/v2 (CVE-2026-54764). Risk of unauthorized operations or information disclosure. Exploitable via req.TLS. Mitigation: upgrade to 2.11.51 or later.

Original description

The description as published by the source.

Summary

There is a medium severity vulnerability in Traefik's ForwardAuth middleware. Even when configured with trustForwardHeader: false, Traefik derives the X-Forwarded-Port header sent to the authentication service from the original incoming request instead of the sanitized forwarded request. As a result, an unauthenticated remote attacker can inject an X-Forwarded-Proto: https header over a plain HTTP connection and cause Traefik to forward X-Forwarded-Port: 443 to the auth service, bypassing port-based authorization checks. This is a regression of the incomplete fix for GHSA-6384-m2mw-rf54, which addressed the X-Forwarded-Proto and X-Forwarded-Prefix spoofing vectors but missed the X-Forwarded-Port vector.

Patches

For more information

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

Original Description

Summary

The ForwardAuth middleware, even when configured with trustForwardHeader: false,
still derives the X-Forwarded-Port header sent to the authentication service by
reading the attacker-controlled X-Forwarded-Proto header from the original
incoming request. This allows an unauthenticated remote attacker to cause Traefik
to forward X-Forwarded-Port: 443 to the auth s…

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-54764 has been found in github.com/traefik/traefik/v2.
Attackers can target a specific entry point like req.TLS over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade github.com/traefik/traefik/v2 to 2.11.51 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik/v2 CVE-2026-54764" on the vendor's site.

CVE-2026-54764 (github.com/traefik/traefik/v2) — CWE-345 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: req.TLS / req / forwardReq
Patched: 2.11.51 — 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-345) exists in github.com/traefik/traefik/v2. Attackers reach the vulnerable code path via req.TLS without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/traefik/traefik/v2. Attack surface: req.TLS / req / forwardReq.

🔥 Severity

Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.11.51.

🛡️ 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/v2' . 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/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/traefik/traefik/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/traefik/traefik/v2 to 2.11.51

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

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

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

Affected packages

go github.com/traefik/traefik/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.11.51"}]}]
go github.com/traefik/traefik/v3
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.6"}]}]
go github.com/traefik/traefik
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.7.34"}]}]

References

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