Answer in brief
CVE-2026-65600 records a High severity (CVSS 7.8) vulnerability in Traefik before v2.11.52 Authentication Bypass via ReplacePathRegex. The current sources do not mark it as known exploited. The current feed maps traefik/traefik (generic), traefik/traefik (generic), traefik/traefik (generic), github.com/traefik/traefik (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 7.8. 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), traefik/traefik (generic), traefik/traefik (generic), github.com/traefik/traefik (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:traefik:traefik:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:a:traefik:traefik:*:-:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| traefik/traefikgeneric | >=0 <2.11.52 | 2.11.52 |
| traefik/traefikgeneric | >=3.6.0 <3.6.23 | 3.6.23 |
| traefik/traefikgeneric | >=3.7.0 <3.7.7 | 3.7.7 |
| github.com/traefik/traefikgo | <=1.7.34 | Not reported |
| github.com/traefik/traefik/v2go | <=2.11.51 | 2.11.52 |
| github.com/traefik/traefik/v3go | <=3.6.22 | 3.6.23 |
| github.com/traefik/traefik/v3go | >=3.7.0,<=3.7.6 | 3.7.7 |
Published upstream
Jul 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
Traefik versions <= v2.11.51, >= v3.6.0 <= v3.6.22, and >= v3.7.0 <= v3.7.6 contain an authentication bypass via path traversal in the ReplacePathRegex middleware. When ReplacePathRegex is configured with a regex that captures user-controlled path segments without a mandatory path separator (e.g. regex "^/api(.*)", replacement "/$1"), the middleware forwards the replaced path to the backend without validating that it matches its normalized form. An unauthenticated remote attacker can send a crafted request (e.g. GET /api../admin) that produces an un-normalized path such as /../admin, which a backend that normalizes paths resolves to a protected route, bypassing authentication middleware. Fixed in v2.11.52, v3.6.23, and v3.7.7.
Quoted source text, attributed separately from HOL analysis.