# CVE-2026-54762: Traefik Kubernetes Ingress NGINX provider fails open when auth-secret resolution fails > Traefik fails open when authentication secrets are missing, allowing unauthenticated access to protected backend services. - **Severity:** Medium 5.9 (`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`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Jun 2026 - **Updated:** 24 Jun 2026 - **Also known as:** GHSA-4mr2-fg2p-w63c, GO-2026-5128, MINI-8c9w-whr5-8q74, MINI-hq6h-6qjj-xg8j, MINI-wh2h-hg5f-gprj ## What is CVE-2026-54762? CVE-2026-54762 is a medium-severity authentication bypass vulnerability in Traefik Traefik, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-693 (Protection Mechanism Failure), CWE-636 (Not Failing Securely) ## Which versions are affected by CVE-2026-54762? 5 open source packages ship an affected version, including github.com/traefik/traefik/v3, github.com/traefik/traefik and github.com/traefik/traefik/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/traefik/traefik/v3` | Go | From 3.7.0-ea.1 | 3.7.5 | | `github.com/traefik/traefik/v3` | Go | From 3.7.0-ea.1 | 3.7.5 | | `github.com/traefik/traefik/v3` | Go | From 3.7.0-ea.1 | 3.7.5 | | `github.com/traefik/traefik` | Go | All versions | None | | `github.com/traefik/traefik/v2` | Go | All versions | None | Products: Traefik Traefik. ## How do I fix CVE-2026-54762? Upgrade github.com/traefik/traefik/v3 to 3.7.5 or later. ## Is CVE-2026-54762 being exploited? There is no known exploitation of CVE-2026-54762 in the wild and no public exploit code. ## Other vulnerabilities in Traefik Traefik - [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8) - [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3) - [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3) - [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1) - [CVE-2026-88009](https://insights.sbomify.com/CVE-2026-88009/): Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-54762 and fix it if it is affected. What it is: CVE-2026-54762 is a medium-severity authentication bypass vulnerability in Traefik Traefik, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-54762 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/traefik/traefik/v3 (Go): affected from 3.7.0-ea.1; fixed in 3.7.5 - github.com/traefik/traefik/v3 (Go): affected from 3.7.0-ea.1; fixed in 3.7.5 - github.com/traefik/traefik/v3 (Go): affected from 3.7.0-ea.1; fixed in 3.7.5 - github.com/traefik/traefik (Go): affected all versions; no fix listed - github.com/traefik/traefik/v2 (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-54762/ (Markdown: https://insights.sbomify.com/CVE-2026-54762/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54762 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54762 - OSV: https://osv.dev/vulnerability/CVE-2026-54762 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-54762/ Summaries are generated and may contain mistakes; the official description above is the record.