traefik · Traefik · published 2026-06-23
CVE-2026-54762Traefik Kubernetes Ingress NGINX provider fails open when auth-secret resolution fails
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-54762 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 38% of all CVEs. This Traefik vulnerability: CVSS 5.9 (v4.0). Fixed upstream in Traefik 3.7.5. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Traefik 3.7.5.
Patch events
Web serverTraefik
Traefik security release: 3.7.5
Upgrade to
3.7.5Why: Vendor security release for server software (most severe: CVE-2026-54762).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (39th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.9 (v4.0)CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- traefik traefik
>= 3.7.0-ea.1, < 3.7.5(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.