Live › vulnerability › CVE-2026-88010
Go to dashboardTraefik's BasicAuth middleware leaks whether a username exists through response timing when many requests run concurrently. An attacker can list valid usernames but cannot read passwords or bypass login.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| github.com/traefik/traefik | go | all versions | – |
traefik version; affected if it is 3.6.11 through 3.7.12 (Traefik v2 and Digest auth are not affected)Upgrade Traefik to 3.7.13 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Traefik is an open source HTTP reverse proxy and load balancer. From 3.6.11 until 3.7.13, checkPassword in pkg/middlewares/auth/basic_auth.go constructs the BasicAuth singleflight key from the submitted password and stored secret. Concurrent requests for absent usernames therefore coalesce on one key while configured usernames perform separate password hashes, creating an unauthenticated timing discrepancy that reveals whether a username exists. Sequential checks remain cost-equalized, Traefik v2 and Digest authentication are not affected, and the issue does not disclose credentials or bypass authentication. This issue is fixed in version 3.7.13.
This page as .md · .json · in your agent: get_signal("CVE-2026-88010")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.