{"id":"GHSA-2272-4vv8-65ww","aliases":[],"summary":"Negated Host matcher causes a TLS option conflict that disables client-certificate authentication on the excluded host","published_at":"2026-10-07T08:47:53Z","modified_at":"2026-10-07T08:47:53Z","products":[{"slug":"traefik","name":"Traefik","category":"proxy"}],"rating":{"severity":"medium","score":6.9,"vector":"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","attack_path":"internet_unauthenticated","user_interaction":false,"malicious":false},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":8.9,"record_count":1,"vendors":["GitHub"],"details":"## Summary\n\nThere 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.\n\nBoth 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.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v2.11.58\n- https://github.com/traefik/traefik/releases/tag/v3.7.13\n\n## For more information\n\nIf you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).","affected_stack":[{"ecosystem":"Go","package":"github.com/traefik/traefik/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v2.11.58"}]}],"fixed":["v2.11.58"],"provider":"github-repo-advisories","source":"GHSA-2272-4vv8-65ww","relation":"self"},{"ecosystem":"Go","package":"github.com/traefik/traefik/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.0.0"},{"fixed":"v3.7.13"}]}],"fixed":["v3.7.13"],"provider":"github-repo-advisories","source":"GHSA-2272-4vv8-65ww","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"github-repo-advisories","source_id":"GHSA-2272-4vv8-65ww","relation":"self","url":"https://github.com/traefik/traefik/security/advisories/GHSA-2272-4vv8-65ww","license":"GitHub Terms of Service","published_at":"2026-10-07T08:47:53Z","modified_at":"2026-10-07T08:47:53Z","summary":"Negated Host matcher causes a TLS option conflict that disables client-certificate authentication on the excluded host","details":"## Summary\n\nThere 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.\n\nBoth 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.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v2.11.58\n- https://github.com/traefik/traefik/releases/tag/v3.7.13\n\n## For more information\n\nIf you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).","severity":[{"type":"CVSS_V4","score":"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","source":"GHSA-2272-4vv8-65ww"}],"affected":[{"ecosystem":"Go","package":"github.com/traefik/traefik/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v2.11.58"}]}],"fixed":["v2.11.58"],"provider":"github-repo-advisories","source":"GHSA-2272-4vv8-65ww","relation":"self"},{"ecosystem":"Go","package":"github.com/traefik/traefik/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.0.0"},{"fixed":"v3.7.13"}]}],"fixed":["v3.7.13"],"provider":"github-repo-advisories","source":"GHSA-2272-4vv8-65ww","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-2272-4vv8-65ww"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-2272-4vv8-65ww"}],"sources":[{"provider":"github-repo-advisories","source_id":"GHSA-2272-4vv8-65ww","url":"https://github.com/traefik/traefik/security/advisories/GHSA-2272-4vv8-65ww","license":"GitHub Terms of Service","modified_at":"2026-10-07T08:47:53Z","relation":"self"}]}
