traefik · Traefik · published 2026-04-30
CVE-2026-41263Traefik: BasicAuth middleware: timing side-channel vulnerability
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-41263 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 31% of all CVEs. This Traefik vulnerability: CVSS 6.3 (v4.0). Fixed upstream in Traefik 3.6.14, 2.11.43. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Traefik 3.6.14, 2.11.43.
Patch events
Web serverTraefik
Traefik security releases: 3.6.14, 2.11.43
Upgrade to
3.6.142.11.43Why: Vendor security release for server software (most severe: CVE-2026-40912).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (32th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.3 (v4.0)CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/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
< 2.11.43(affected)>= 3.0.0-beta1, < 3.6.14(affected)>= 3.7.0-ea.1, < 3.7.0-rc.2(affected)
Description (from the CVE record)#
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a timing side-channel vulnerability in Traefik's BasicAuth middleware that allows an attacker to enumerate valid usernames through response-time differences. The variable intended to hold a constant-time fallback secret always resolves to an empty string, causing the constant-time comparison to short-circuit in microseconds rather than performing a full bcrypt evaluation. This restores the original timing oracle and makes it possible to distinguish existing users from non-existing ones by measuring authentication response times. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
Quoted from the CVE Program record.