← Übersicht Traefik

Negated Host matcher causes a TLS option conflict that disables client-certificate authentication on the excluded host

GHSA-2272-4vv8-65ww

Mittel · CVSS 6.9 Netzwerk · ohne Login Fix verfügbar

Veröffentlicht
07.10.2026 10:47
Zuletzt geändert
07.10.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:L/SA:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

## Summary There is a medium severity vulnerability in Traefik's TLS options resolution: a negated `Host` matcher in a router rule (for example ``PathPrefix(`/`) && !Host(`secure.example.com`)``) is still counted as a host served by that router when the domains are deduced from the rule. When another router actually serves that host with non-default `tls.options`, Traefik sees two routers claiming the same host with different TLS options, declares a conflict, and falls back to the `default` TLS options for both. Because the `default` options request no client certificate, a `RequireAndVerifyClientCert` policy stops being enforced on that host and an unauthenticated client can reach the protected backend. The downgrade is reported at `ERROR` level in the logs, and setting `core.strictTLSOptions=true` disables the fallback and mitigates the issue. Both the v2 and v3 lines are affected. Traefik v3 versions below v3.7 are affected but are no longer maintained and will not receive a patch of their own; the remedy for those users is to upgrade to a maintained, patched version. ## Patches - https://github.com/traefik/traefik/releases/tag/v2.11.58 - https://github.com/traefik/traefik/releases/tag/v3.7.13 ## 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.58GHSA-2272-4vv8-65ww
Gogithub.com/traefik/traefik/v3v3.0.0 → v3.7.13GHSA-2272-4vv8-65ww

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.