CVE-2026-88010·Traefik vulnerability
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.
- Severity
- medium
- Software
- Traefik
- Fixed in
- 3.7.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.69% — higher than 51% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 3.6.11
Until: 3.7.13
Fixed in: 3.7.13
How to fix this CVE
Upgrade Traefik to version 3.7.13 or later to address a timing-based username enumeration vulnerability in the BasicAuth middleware. This fix prevents attackers from determining valid usernames through response time analysis on concurrent authentication requests. Organizations running affected versions (3.6.11 through 3.7.13) should prioritize this update as part of their regular patching cycle.
sudo dnf update traefikDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check installed Traefik version with 'traefik version' or 'docker exec <container-id> traefik version' for containerized deployments
- Step 2: Verify BasicAuth middleware is enabled in your Traefik configuration by searching for 'basicAuth' in your traefik.yml or docker-compose.yml files
- Step 3: Review access logs for patterns of repeated failed authentication attempts to non-existent usernames followed by successful attempts to valid usernames with timing differences
- Step 4: After upgrading, confirm the new version with 'traefik version' and validate BasicAuth configuration still functions with a test login attempt
FAQ
What is CVE-2026-88010?
CVE-2026-88010 is a timing-based information disclosure vulnerability in Traefik's BasicAuth middleware where concurrent authentication requests for non-existent usernames are coalesced into a single password hash operation, while valid usernames perform separate hashes. This timing difference allows attackers to enumerate which usernames exist in the system without valid credentials.
Is CVE-2026-88010 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available. However, the attack technique is straightforward for determined threat actors.
What versions of Traefik are affected by CVE-2026-88010?
Traefik versions 3.6.11 through 3.7.12 are vulnerable. The fix is available in version 3.7.13 and later. Traefik v2 and Digest authentication implementations are not affected.
How do I check if my server is vulnerable to CVE-2026-88010?
Run 'traefik version' and compare the output to version 3.7.13. If you're running version 3.6.11 or later but below 3.7.13, and BasicAuth is enabled in your configuration, your system is vulnerable.
Does Defensia detect CVE-2026-88010?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Traefik is installed on a monitored server, CVE-2026-88010 will appear in your dashboard with remediation steps.
Related Traefik CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-88010. Free for 1 server.
Get started free