Homepage

Not Failing Securely ('Failing Open') Affecting traefik-3 package, versions <3.7.5-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.41% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-TRAEFIK3-17390957
  • published21 Jun 2026
  • disclosed23 Jun 2026
Report a new vulnerability Found a mistake?

Introduced: 21 Jun 2026

CVE-2026-54762  (opens in a new tab)
CWE-636  (opens in a new tab)
CWE-693  (opens in a new tab)

How to fix?

Upgrade Minimos:latest traefik-3 to version 3.7.5-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream traefik-3 package and not the traefik-3 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Traefik is an HTTP reverse proxy and load balancer. From 3.7.0-ea.1 until 3.7.5, there is a medium severity vulnerability in Traefik's Kubernetes Ingress NGINX provider that causes affected routes to fail open. When an Ingress explicitly enables BasicAuth or DigestAuth through the supported nginx.ingress.kubernetes.io/auth-type and auth-secret annotations, but the referenced auth Secret cannot be resolved or parsed, Traefik logs the resolution error, skips installing the authentication middleware, and still emits a router to the backend service. A route that operators intended to protect is therefore published to the data plane without its authentication control, allowing unauthenticated access to the backend. The trigger is an invalid or unresolved auth dependency — a missing, malformed, unreadable, or policy-denied Secret — rather than an intentionally unprotected route. This vulnerability is fixed in 3.7.5.