CVE-2026-54764 traefik vulnerability
Traefik is an HTTP reverse proxy and load balancer. Prior to v2.11.51, v3.6.22, and v3.7.6, Traefik's ForwardAuth middleware, even when configured with trustForwardHeader: false, 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 authentication service, bypassing port-based authorization checks. This issue is fixed in versions v2.11.51, v3.6.22, and v3.7.6.
Quick answer
traefik should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Traefik is affected by CVE-2026-54764, a header trust and authorization bypass risk. Traefik is an HTTP reverse proxy and load balancer. The recommended remediation is to update to Traefik 2.11.51, 3.6.22, 3.7.6, or a later fixed release for the deployed branch. Until the update is complete, sanitize forwarded headers before ForwardAuth and block client-controlled X-Forwarded-* headers at the edge, review logs, and reduce exposure of the affected service or workflow.
- Inventory every deployment, package, appliance, container, service, and managed environment that uses Traefik.
- Confirm the installed version and compare it with versions prior to v2 and the source advisory for CVE-2026-54764.
- Apply the vendor-supported fix: update to Traefik 2.11.51, 3.6.22, 3.7.6, or a later fixed release for the deployed branch.
- If the update cannot be applied immediately, sanitize forwarded headers before ForwardAuth and block client-controlled X-Forwarded-* headers at the edge; disable unnecessary public access, endpoints, integrations, uploads, management interfaces, or high-risk features until patched.
- Review application, device, reverse-proxy, WAF, package manager, container, authentication, and audit logs for activity related to CVE-2026-54764.
- Rotate sessions, API tokens, service credentials, integration keys, and administrator passwords if logs or affected data indicate compromise, code execution, credential exposure, or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or appliances when appropriate, and remove temporary files, stored payloads, generated artifacts, or unsafe configuration created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Traefik now reports Traefik 2.11.51, 3.6.22, 3.7.6, or a later fixed release for the deployed branch or a later vendor-supported fixed release for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-54764, using a safe regression test or vendor-provided validation method.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, file access, credential exposure, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, device health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup or credential rotation performed.
Trusted references
FAQ
What is affected by CVE-2026-54764?
traefik should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.