GHSA-p8wx-ph99-xgcr: Traefik 3.7.0-ea.1 before 3.7.15 mTLS Bypass via Ingress NGINX Provider

Published Oct 30, 2026
·
Updated

Traefik from 3.7.0-ea.1 before 3.7.15 contains an authentication bypass vulnerability in the Kubernetes Ingress NGINX provider that silently disables mTLS configured via the auth-tls-secret annotation. When another Ingress declares a path on the same host without matching auth-tls settings, Traefik falls back to default TLS options, letting unauthenticated attackers reach backends requiring client certificates.

Affected Software

1 affected component
Traefik traefik>=3.7.0-ea.1<3.7.15

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Traefik to a version that resolves this vulnerability.

    Fixed in 3.7.15

Event History

Oct 30, 2026
CVE Published
via OSV·01:18 PM
Data Sourced
via OSV·01:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments using Traefik’s Kubernetes Ingress NGINX provider are exposed when mTLS is configured with the auth-tls-secret annotation and another Ingress declares a path on the same host without matching auth-tls settings.

2

What does an attacker need to exploit this issue?

An attacker does not need authentication or user interaction. They need to reach a backend through the affected shared host configuration, where Traefik has fallen back to its default TLS options instead of enforcing client certificates.

3

Is mTLS disabled for every Ingress by default?

No. The described bypass depends on conflicting or incomplete auth-tls settings across Ingress resources that declare paths for the same host. The issue occurs when the other Ingress does not have matching auth-tls settings.

4

How can I identify potentially affected configurations?

Review Ingress resources handled by the Kubernetes Ingress NGINX provider and group them by host. Flag hosts where an Ingress uses auth-tls-secret but another Ingress declares a path for that host without matching auth-tls configuration.

5

What should be done if patching is not immediately possible?

Avoid placing paths from Ingress resources with different auth-tls settings on the same host. Ensure every Ingress declaring paths for a host protected by auth-tls-secret has matching auth-tls settings until the affected Traefik version is replaced.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203