{"id":"GHSA-qvj7-gq9c-hp7q","aliases":[],"summary":"Kubernetes Ingress NGINX provider: ssl-passthrough sibling HTTP router serves the auth-protected backend without auth","published_at":"2026-10-07T08:47:51Z","modified_at":"2026-10-07T08:47:51Z","products":[{"slug":"traefik","name":"Traefik","category":"proxy"}],"rating":{"severity":"high","score":7,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N","attack_path":"internet_unauthenticated","user_interaction":false,"malicious":false},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":9,"record_count":1,"vendors":["GitHub"],"details":"## Summary\n\nThere is a high severity vulnerability in Traefik's Kubernetes Ingress NGINX provider. Since v3.7.13, an Ingress carrying the `nginx.ingress.kubernetes.io/ssl-passthrough: \"true\"` annotation gets, besides its TCP passthrough router, an HTTP router on the non-TLS entry points that proxies to the backend. That router was built outside the regular per-rule processing, so the access-control annotations set on the same Ingress, such as `auth-type` with `auth-secret`, `auth-url` and `whitelist-source-range`, were parsed but never turned into middlewares on it. An unauthenticated client reaching the HTTP entry point with the Ingress host could therefore reach a backend the operator had annotated as protected, with no authentication and no source allow-listing applied, and nothing logged. The HTTP side of an ssl-passthrough Ingress is now built like any other Ingress, with its annotation directives applied; the routers it generates are renamed as a result, see the v3.7.14 migration guide. Traefik v2 and Traefik v3 versions before v3.7.13 are not affected.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v3.7.14\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/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.7.13"},{"fixed":"v3.7.14"}]}],"fixed":["v3.7.14"],"provider":"github-repo-advisories","source":"GHSA-qvj7-gq9c-hp7q","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"github-repo-advisories","source_id":"GHSA-qvj7-gq9c-hp7q","relation":"self","url":"https://github.com/traefik/traefik/security/advisories/GHSA-qvj7-gq9c-hp7q","license":"GitHub Terms of Service","published_at":"2026-10-07T08:47:51Z","modified_at":"2026-10-07T08:47:51Z","summary":"Kubernetes Ingress NGINX provider: ssl-passthrough sibling HTTP router serves the auth-protected backend without auth","details":"## Summary\n\nThere is a high severity vulnerability in Traefik's Kubernetes Ingress NGINX provider. Since v3.7.13, an Ingress carrying the `nginx.ingress.kubernetes.io/ssl-passthrough: \"true\"` annotation gets, besides its TCP passthrough router, an HTTP router on the non-TLS entry points that proxies to the backend. That router was built outside the regular per-rule processing, so the access-control annotations set on the same Ingress, such as `auth-type` with `auth-secret`, `auth-url` and `whitelist-source-range`, were parsed but never turned into middlewares on it. An unauthenticated client reaching the HTTP entry point with the Ingress host could therefore reach a backend the operator had annotated as protected, with no authentication and no source allow-listing applied, and nothing logged. The HTTP side of an ssl-passthrough Ingress is now built like any other Ingress, with its annotation directives applied; the routers it generates are renamed as a result, see the v3.7.14 migration guide. Traefik v2 and Traefik v3 versions before v3.7.13 are not affected.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v3.7.14\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:H/SA:N","source":"GHSA-qvj7-gq9c-hp7q"}],"affected":[{"ecosystem":"Go","package":"github.com/traefik/traefik/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"v3.7.13"},{"fixed":"v3.7.14"}]}],"fixed":["v3.7.14"],"provider":"github-repo-advisories","source":"GHSA-qvj7-gq9c-hp7q","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-qvj7-gq9c-hp7q"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/traefik/traefik/security/advisories/GHSA-qvj7-gq9c-hp7q"}],"sources":[{"provider":"github-repo-advisories","source_id":"GHSA-qvj7-gq9c-hp7q","url":"https://github.com/traefik/traefik/security/advisories/GHSA-qvj7-gq9c-hp7q","license":"GitHub Terms of Service","modified_at":"2026-10-07T08:47:51Z","relation":"self"}]}
