- Veröffentlicht
- 12.11.2026 11:01
- Zuletzt geändert
- 12.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
## Summary
There is a vulnerability in Traefik's request path sanitization. The `sanitizePath` entry point option, enabled by default, resolves the `..` and `.` dot-segments and removes the duplicate slashes from the request path before routing, but it leaves a dot-segment carrying a path parameter, such as `/..;x/`, untouched. Traefik matches its routers and applies its middlewares on this unresolved path and forwards it unchanged. When a backend that strips path parameters (Servlet containers, Spring, ...) is shared between an unauthenticated router and a router protected by an authentication or authorization middleware, an unauthenticated attacker can send a single request such as `/public/..;x/admin` to reach the protected resources and bypass the middleware.
Traefik v2.11.62, v3.7.18 and v3.8.0-rc.2 resolve the `..`, `.` and empty segments carrying path parameters before the dot-segment removal, when `sanitizePath` is enabled (the default). Traefik v3.0 to v3.6 are also affected; these lines are end of life and will not receive a patch, the remedy is to upgrade to a patched release.
## Patches
- https://github.com/traefik/traefik/releases/tag/v2.11.62
- https://github.com/traefik/traefik/releases/tag/v3.7.18
- https://github.com/traefik/traefik/releases/tag/v3.8.0-rc.2
## For more information
If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).
Betroffene Pakete im beobachteten Stack
Gogithub.com/traefik/traefik/v2v2.11.62GHSA-cp28-5662-543f
Gogithub.com/traefik/traefik/v3v3.0.0 → v3.7.18GHSA-cp28-5662-543f
Gogithub.com/traefik/traefik/v3v3.8.0-rc.1 → v3.8.0-rc.2GHSA-cp28-5662-543f
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.