- 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 vulnerability in Traefik's Kubernetes Ingress NGINX provider when several Ingresses share a host configured for client certificate authentication with the `nginx.ingress.kubernetes.io/auth-tls-secret` annotation. Since v3.7.15 the client authentication applies to the whole host and the TLS handshake uses the settings of the first Ingress declaring it, but the `Ssl-Client-*` headers were still built from the annotations of each Ingress: an Ingress with `auth-tls-verify-client: on` sharing a host with an Ingress using `optional_no_ca` forwarded `Ssl-Client-Verify: SUCCESS`, together with the subject and issuer chosen by the client, for a certificate that was never verified, and an Ingress without its own `auth-tls-secret` or without `auth-tls-pass-certificate-to-upstream` had no middleware handling these headers, so the values sent by the client reached the backend. An unauthenticated remote client can therefore present a forged client identity to a backend that trusts the proxy's verification result.
The issue was introduced in v3.7.15; earlier versions are not affected, and Traefik v2 is not affected since it does not include the Kubernetes Ingress NGINX provider.
## Patches
- 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/v3v3.7.15 → v3.7.18GHSA-ccgh-9g52-6vwg
Gogithub.com/traefik/traefik/v3v3.8.0-rc.1 → v3.8.0-rc.2GHSA-ccgh-9g52-6vwg
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.