CVE-2026-48020: Traefik StripPrefix Route-Level Auth Bypass via Path Normalization
Traefik is an HTTP reverse proxy and load balancer. Prior to 2.11.48, 3.6.19, and 3.7.3, there is a high severity vulnerability in Traefik's StripPrefix middleware that allows an unauthenticated attacker to bypass route-level authentication and authorization. When a public router matches on a PathPrefix rule and applies the StripPrefix middleware, a request path containing .. or its percent-encoded form %2e%2e can match the public route at routing time and then, after the prefix is stripped and the path is normalized, resolve to a path served by a separate, authenticated router. As a result, an attacker can reach protected backend paths — such as admin or internal configuration endpoints — without satisfying the authentication middleware attached to the protected router. This vulnerability is fixed in 2.11.48, 3.6.19, and 3.7.3.
Security readout for executives and security teams
Plain-English summary
A crafted web request can enter through a public Traefik route and reach a protected backend path without passing that route’s authentication checks. Successful abuse could expose or alter sensitive administrative or internal information. Risk depends on using affected Traefik versions with the specific PathPrefix and StripPrefix routing pattern.
Executive priority
Treat affected, externally reachable configurations as an emergency patching priority because exploitation needs no credentials or user interaction and may compromise sensitive data or settings. Prioritize systems exposing administrative or internal backend paths. Validate configuration exposure before lowering urgency.
Technical view
Traefik evaluates a PathPrefix public router before StripPrefix processing and path normalization. Paths containing parent-directory segments, including their percent-encoded form, can initially match the public router, then normalize to a resource associated with a separate authenticated router. This creates route-level authentication and authorization bypass with high confidentiality and integrity impact.
Likely exposure
Exposure requires an affected Traefik version and a public PathPrefix router using StripPrefix where normalization can resolve requests to protected backend paths. Internet-reachable deployments with adjacent public and authenticated routes deserve immediate review. Deployments without this routing pattern may not be exploitable through this issue.
Exploitation context
The CVSS 3.1 score is 9.1: network-accessible, low complexity, unauthenticated, and requiring no user interaction. The supplied record marks KEV as false, and the source bundle provides no evidence of active exploitation. This does not establish that exploitation is absent.
Researcher notes
The defect combines path traversal semantics with an alternate authentication path: routing authorization occurs against one path interpretation, while the backend target is selected after prefix removal and normalization. Assessment should focus on middleware order, public PathPrefix matches, shared backends, and protected paths. Availability impact is not claimed by the supplied CVSS vector.
Mitigation direction
Upgrade Traefik 2.x deployments to 2.11.48 or later.
Upgrade Traefik 3.6 deployments to 3.6.19 or later.
Upgrade Traefik 3.7 deployments to 3.7.3 or later.
Review vendor guidance if immediate upgrading is operationally impossible.
Restrict public access to sensitive backend endpoints while remediation is pending.
Validation and detection
Inventory all Traefik instances and compare versions with the documented affected ranges.
Identify public PathPrefix routers that apply StripPrefix middleware.
Map those routers to backends also serving authenticated administrative or internal paths.
Confirm upgraded instances report a fixed or later Traefik version.
Review proxy and backend logs for abnormal parent-directory or encoded-dot path patterns.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.