CVE-2026-88009: Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging

Published Sep 10, 2026
·
Updated

Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.57, and 3.7.13, Traefik accepts a rootless HTTP/1 request target that Go stores in URL.Opaque while leaving URL.Path empty. The rewriteRequestBuilder path evaluates routing, path sanitization, forwardAuth, encodedCharacters, and access logging against a path normalized to / but forwards URL.Opaque verbatim to the backend, allowing cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion when the backend interprets the opaque target as a path. This issue is fixed in 2.11.57 and 3.7.13.

Affected Software

1 affected component
Traefik traefik>0<=2.11.56, >0<=3.7.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Traefik to a version that resolves this vulnerability.

    Fixed in 2.11.57
  2. Upgrade

    Upgrade Traefik to a version that resolves this vulnerability.

    Fixed in 3.7.13

Event History

Sep 10, 2026
CVE Published
via MITRE·03:01 PM
Data Sourced
via MITRE·03:01 PM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Traefik deployments running versions earlier than 2.11.57 or 3.7.13 are affected when they accept HTTP/1 requests and forward requests to a backend that interprets an opaque request target as a path.

2

What does an attacker need to send?

An attacker needs to submit an HTTP/1 request with a rootless request target. Traefik evaluates the request as though its path were "/", while forwarding the opaque target verbatim to the backend.

3

How can I determine whether an instance needs remediation?

Check the deployed Traefik version. Instances on the 2.11 release line need to be updated to 2.11.57 or later, and instances on the 3.7 release line need to be updated to 3.7.13 or later.

4

What is the impact if a vulnerable request reaches a compatible backend?

The request can bypass path-scoped routing and authorization controls, including middleware guards such as forwardAuth. Access logging can record the normalized "/" path rather than the path interpreted by the backend.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203