← Übersicht Traefik

Incomplete fix for GHSA-hrpp-p4fc-wwf8 allows ForwardAuth NTLM authentication bypass via Proxy-Authorization

GHSA-p956-6gvv-mxqp

Hoch · CVSS 7.0 Netzwerk · ohne Login Fix verfügbar

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: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 high severity authentication vulnerability in Traefik's ForwardAuth middleware when the authentication server uses a connection-bound scheme such as NTLM or SPNEGO/Kerberos "Negotiate". The fix for GHSA-hrpp-p4fc-wwf8 sends the subrequests of a client that presents such a credential on a dedicated connection to the authentication server, but it only detects the credential in the `Authorization` header. ForwardAuth also forwards the `Proxy-Authorization` header, and a credential sent in that header still goes through the connection pool shared by every client. An unauthenticated client can then reuse an authentication-server connection already authenticated by another user, receive that user's identity through `authResponseHeaders`, and access the backend as that user. The patched versions apply the same isolation to `Proxy-Authorization`. Traefik v3.0 through v3.6 are end-of-life and are also affected; they will not receive a fix on their own line. As a workaround, set `authRequestHeaders` to a list that does not include `Proxy-Authorization`. ## 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-p956-6gvv-mxqp
Gogithub.com/traefik/traefik/v3v3.0.0 → v3.7.18GHSA-p956-6gvv-mxqp
Gogithub.com/traefik/traefik/v3v3.8.0-rc.1 → v3.8.0-rc.2GHSA-p956-6gvv-mxqp

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. 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.