{"id":"CVE-2026-85596","aliases":[],"summary":"Traefik v3.7 Authentication Bypass via TLS Option Conflict","published_at":"2026-09-04T11:30:00.112Z","modified_at":"2026-10-08T15:51:48.871Z","products":[],"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,"red_hat":"Important","vendor_ratings":[{"source":"Red Hat","rating":"Important"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.004350000061094761,"percentile":0.385560005903244,"date":"2026-11-19T00:00:00Z"},"priority":10.2,"details":"Traefik versions >= v3.7.0 and <= v3.7.10 contain an authentication bypass in the 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. As a result, two Ingress objects sharing the same host, the same client CA secret, and the same client-authentication mode produced two distinct TLS option names for that host. Traefik treats this 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 a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.","affected_stack":[],"affected_other":[{"ecosystem":"CVE","package":"traefik/traefik","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.7.0"},{"last_affected":"3.7.10"}]}],"provider":"cvelistv5","source":"CVE-2026-85596","relation":"self"},{"ecosystem":"NVD","package":"traefik:traefik","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.7.0"},{"fixed":"3.7.11"}]}],"fixed":["3.7.11"],"provider":"nvd","source":"CVE-2026-85596","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"Red Hat OpenShift Dev Spaces","cpe":"cpe:/a:redhat:openshift_devspaces:3","status":"not_affected","packages":["devspaces/traefik-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-85596"},{"vendor":"Red Hat","product":"Red Hat OpenShift GitOps","cpe":"cpe:/a:redhat:openshift_gitops:1","status":"not_affected","packages":["openshift-gitops-1/argo-rollouts-rhel8","openshift-gitops-1/argo-rollouts-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-85596"}],"records":[{"provider":"cvelistv5","source_id":"CVE-2026-85596","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-85596","license":"CC-BY-4.0","published_at":"2026-09-04T11:30:00.112Z","modified_at":"2026-10-08T15:51:48.871Z","summary":"Traefik v3.7 Authentication Bypass via TLS Option Conflict","details":"Traefik versions >= v3.7.0 and <= v3.7.10 contain an authentication bypass in the 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. As a result, two Ingress objects sharing the same host, the same client CA secret, and the same client-authentication mode produced two distinct TLS option names for that host. Traefik treats this 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 a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.","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":"CVE-2026-85596"}],"affected":[{"ecosystem":"CVE","package":"traefik/traefik","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.7.0"},{"last_affected":"3.7.10"}]}],"provider":"cvelistv5","source":"CVE-2026-85596","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq"},{"type":"WEB","url":"https://www.vulncheck.com/advisories/traefik-3.7-authentication-bypass-via-tls-option-conflict"}]},{"provider":"nvd","source_id":"CVE-2026-85596","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-85596","severity":[],"affected":[{"ecosystem":"NVD","package":"traefik:traefik","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.7.0"},{"fixed":"3.7.11"}]}],"fixed":["3.7.11"],"provider":"nvd","source":"CVE-2026-85596","relation":"self"}],"product_status":[],"references":[]},{"provider":"redhat-vex","source_id":"CVE-2026-85596","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2026-85596","license":"CC-BY-4.0","published_at":"2026-09-04T11:30:00.112Z","modified_at":"2026-09-16T20:50:13Z","summary":"github.com/traefik/traefik: Traefik: Authentication bypass due to TLS configuration conflict","details":"A flaw was found in Traefik. This vulnerability allows a remote attacker to bypass authentication, gaining unauthorized access to protected routes. This occurs due to a conflict in how Traefik handles Transport Layer Security (TLS) options when specific Kubernetes Ingress objects are configured. The conflict causes Traefik to use a less secure default configuration, negating the requirement for client certificates.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","source":"CVE-2026-85596"},{"type":"Red Hat","score":"Important","source":"CVE-2026-85596"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat OpenShift Dev Spaces","cpe":"cpe:/a:redhat:openshift_devspaces:3","status":"not_affected","packages":["devspaces/traefik-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-85596"},{"vendor":"Red Hat","product":"Red Hat OpenShift GitOps","cpe":"cpe:/a:redhat:openshift_gitops:1","status":"not_affected","packages":["openshift-gitops-1/argo-rollouts-rhel8","openshift-gitops-1/argo-rollouts-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-85596"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-85596.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-85596"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2529028"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-85596"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-85596"},{"type":"WEB","url":"https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq"},{"type":"WEB","url":"https://www.vulncheck.com/advisories/traefik-3.7-authentication-bypass-via-tls-option-conflict"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq"},{"type":"WEB","url":"https://www.vulncheck.com/advisories/traefik-3.7-authentication-bypass-via-tls-option-conflict"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-85596.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-85596"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2529028"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-85596"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-85596"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2026-85596","url":"https://www.cve.org/CVERecord?id=CVE-2026-85596","license":"CC-BY-4.0","modified_at":"2026-10-08T15:51:48.871Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2026-85596","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-85596","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2026-85596","url":"https://access.redhat.com/security/cve/CVE-2026-85596","license":"CC-BY-4.0","modified_at":"2026-09-16T20:50:13Z","relation":"self"}]}
