- Veröffentlicht
- 08.10.2026 14:56
- Zuletzt geändert
- 08.10.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
## Summary
There is a critical severity vulnerability in Traefik Hub's `OIDC` and `OAuthClientCreds` middlewares. When the `OIDC` middleware uses a KV session store, the session identifier placed in the cookie is derived from the issuer and the subject of the user with a non-keyed, non-cryptographic hash, so anyone knowing these two non-secret values can compute the cookie of a user whose session is still live and replay it to be served with that user's identity. In addition, the data the middlewares store outside the gateway (session cookies, state cookies, KV session data and cached OAuth tokens) is encrypted with AES in CTR mode, which provides no integrity check, the CSRF token of the `OIDC` middleware is signed with the non-cryptographic FNV-1a hash, and the token cache key of the `OAuthClientCreds` middleware is an unkeyed FNV-1a hash of the client credentials, which allows crafting credentials that collide with another client and being served its cached access token.
Hub versions earlier than the patched ones are affected, including the versions of unmaintained lines, which will not receive a patch: upgrading to a patched, maintained line is the only remediation.
## Patches
- https://github.com/traefik/hub/releases/tag/v3.20.14
- https://github.com/traefik/hub/releases/tag/v3.21.1
Session and state cookies, KV sessions and cached tokens written before the upgrade cannot be decoded by the patched versions: users log in once more and the middleware fetches one fresh token. No configuration change is required.
## For more information
If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/hub-issues/issues).
Betroffene Pakete im beobachteten Stack
GitHubtraefik/hub/Traefik Hub3.20.14GHSA-ph32-mphh-f777
GitHubtraefik/hub/Traefik Hub3.21.0 → 3.21.1GHSA-ph32-mphh-f777
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.