CVE-2026-41263 json
Traefik: BasicAuth middleware: timing side-channel vulnerability
published 6mo ago modified 4mo ago also EUVD-2026-26433 , GHSA-6x2q-h3cr-8j2h , GO-2026-5195
- cvss
- 3.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/traefik/traefik/v3 3.6.14, 3.7.0-rc.2
- go github.com/traefik/traefik/v2 2.11.43
- traefik traefik 2.11.43, 3.6.14, 3.7.0-rc.2
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
- traefik openSUSE Tumbleweed 3.6.15-1.1
- traefik2 openSUSE Tumbleweed 2.11.44-1.1
opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:10697-1openSUSE-SU-2026:10698-1
Is CVE-2026-41263 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-41263 updated cvss 5.3
github.com/traefik/traefik: Traefik: Username enumeration via timing side-channel in BasicAuth middleware
-
Red Hat OpenShift Dev Spaces devspaces/traefik-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | 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 |
| GitHub | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 4.0 | 6.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/traefik/traefik/v3 | >=3.7.0-ea.1, <3.7.0-rc.2 >=3.0.0-beta1, <3.6.14 |
3.7.0-rc.2 3.6.14 |
| go | github.com/traefik/traefik/v2 | <2.11.43 |
2.11.43 |
| go | github.com/traefik/traefik | <=1.7.34 all versions |
no fix listed |
Affected products
- traefik traefik
Classification
- Weakness
-
- CWE-208 Observable Timing Discrepancy
References
-
github.com
/traefik/traefik/security/advisories/GHSA-6x2q-h3cr-8j2h
web, patch, vendor-advisory, advisory
-
github.com
/traefik/traefik/releases/tag/v2.11.43
web, product, release-notes
-
github.com
/traefik/traefik/releases/tag/v3.6.14
web, product, release-notes
-
github.com
/traefik/traefik/releases/tag/v3.7.0-rc.2
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-41263
advisory
-
github.com
/traefik/traefik
package
Sources
- CVE List CVE-2026-41263
- GitHub Advisory GHSA-6x2q-h3cr-8j2h
- NVD CVE-2026-41263
- OSV GO-2026-5195
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.