Answer in brief
CVE-2026-48020 records a Critical severity (CVSS 10.0) vulnerability in Traefik StripPrefix Route-Level Auth Bypass via Path Normalization. The current sources do not mark it as known exploited. The current feed maps traefik/traefik (generic), github.com/traefik/traefik/v2 (go), github.com/traefik/traefik/v2 (go), github.com/traefik/traefik/v3 (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps traefik/traefik (generic), github.com/traefik/traefik/v2 (go), github.com/traefik/traefik/v2 (go), github.com/traefik/traefik/v3 (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| traefik/traefikgeneric | >= 3.7.0-ea.1, < 3.7.3 || >= 3.0.0-beta1, < 3.6.19 || < 2.11.48 | Not reported |
| github.com/traefik/traefik/v2go | <2.11.48 | 2.11.48 |
| github.com/traefik/traefik/v2go | >=0 <2.11.48 | 2.11.48 |
| github.com/traefik/traefik/v3go | <3.6.19 | 3.6.19 |
| github.com/traefik/traefik/v3go | >=3.7.0-ea.1,<3.7.3 | 3.7.3 |
| github.com/traefik/traefik/v3go | >=0 <3.6.19 | 3.6.19 |
| github.com/traefik/traefik/v3go | >=3.7.0-ea.1 <3.7.3 | 3.7.3 |
Published upstream
Jun 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.