Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-53622 critical CVSS 10.0

Vulnerability in Traefik (CVE-2026-53622)

Summary

Vulnerability in Traefik (CVE-2026-53622). Confidential information can be exposed externally. Exploitable via Host. Mitigation: upgrade to 3.7.3 or later.

Original description

The description as published by the source.

Summary

There is a critical vulnerability in Traefik's HTTP/3 (QUIC) TLS configuration selection that allows unauthenticated clients to bypass router-specific mTLS enforcement. When HTTP/3 is enabled on an entrypoint, the TLS handshake selects the applicable TLS configuration through an exact, case-sensitive lookup on the SNI value, which fails to match wildcard host patterns (e.g., *.example.com) or case variants of the configured hostname. Because the handshake falls back to the default TLS configuration — which may not require client certificates — a client can complete the QUIC handshake without presenting a certificate, while the subsequent HTTP routing layer still dispatches the request to a backend protected by a router-specific mTLS policy. The issue affects deployments where HTTP/3 is enabled, a router uses a wildcard Host rule or case-insensitive hostname matching, a router-specific TLSOptions enforces client certificate authentication, and UDP access to the entrypoint is reachable by an attacker.

Patches

For more information

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

Original Description

Summary

Traefik's HTTP/3 TLS configuration selection can ignore router-specific TLSOptions and allow unauthenticated clients to bypass mTLS. The QUIC/HTTP3 p…

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

CVE-2026-53622 (Traefik) — CWE-288 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Host / TLSOptions / API.EXAMPLE.COM / api.example.com
Patched: 3.7.3 — 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-288) exists in Traefik. Attackers reach the vulnerable code path via Host without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Traefik. Attack surface: Host / TLSOptions / API.EXAMPLE.COM / api.example.com.

🔥 Severity

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

🔧 How to fix

Update to 3.7.3.

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

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

  2. 2
    Apply patch patch 
    Upgrade Traefik to 3.7.3

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

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

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

Affected packages

go Traefik
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.3"}]}]
go github.com/traefik/traefik/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.51"}]}]
go github.com/traefik/traefik
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go github.com/traefik/traefik/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.18"}]}]

References

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