https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:10:45 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-85596 <p>Traefik versions &gt;= v3.7.0 and &lt;= 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&#39;s default TLS configuration, which does not request a client certificate, so a route configured with nginx.ingress.kubernetes.io/auth-tls-verify-client: &#34;on&#34; becomes reachable without a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.</p> <p>Traefik versions &gt;= v3.7.0 and &lt;= 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&#39;s default TLS configuration, which does not request a client certificate, so a route configured with nginx.ingress.kubernetes.io/auth-tls-verify-client: &#34;on&#34; becomes reachable without a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-85596 https://vulnerability.circl.lu/vuln/ghsa-rgpg-cpwg-4f45 <p>Traefik versions &gt;= v3.7.0 and &lt;= 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&#39;s default TLS configuration, which does not request a client certificate, so a route configured with nginx.ingress.kubernetes.io/auth-tls-verify-client: &#34;on&#34; becomes reachable without a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.</p> <p>Traefik versions &gt;= v3.7.0 and &lt;= 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&#39;s default TLS configuration, which does not request a client certificate, so a route configured with nginx.ingress.kubernetes.io/auth-tls-verify-client: &#34;on&#34; becomes reachable without a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.</p> https://vulnerability.circl.lu/vuln/ghsa-rgpg-cpwg-4f45