Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3

Traefik: A timing side-channel vulnerability allows for valid username enumeration via BasicAuth middleware

CVE-2026-41263GHSA-6x2q-h3cr-8j2h

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/traefik/traefik/v3

    Affected
    >= 3.7.0-ea.1, < 3.7.0-rc.2>= 3.0.0-beta1, < 3.6.14
    Fixed in
    3.7.0-rc.2, 3.6.14

  • Go github.com/traefik/traefik/v2

    Affected
    < 2.11.43
    Fixed in
    2.11.43

  • Go github.com/traefik/traefik

    Affected
    <= 1.7.34
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 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 · score source
EPSS
  • CVE-2026-41263: 0.37% estimated exploitation activity in the next 30 days; percentile 30.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Patches - https://github.com/traefik/traefik/releases/tag/v2.11.43 - https://github.com/traefik/traefik/releases/tag/v3.6.14 - https://github.com/traefik/traefik/releases/tag/v3.7.0-rc.2 For more information If there are any questions or comments about this advisory, please open an issue. <details <summaryOriginal Description</summary BasicAuth Timing Regression: CVE-2026-32595 Fix Is a No-Op Due to Map Key/Value Confusion TL;DR The patch for…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6x2q-h3cr-8j2h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41263

Advisory: Traefik: A timing side-channel vulnerability allows for valid username enumeration via BasicAuth middleware
IDs: CVE-2026-41263, GHSA-6x2q-h3cr-8j2h
Record: https://patchnext.com/advisories/cve-2026-41263 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/traefik/traefik/v3 3.7.0-rc.2, 3.6.14; github.com/traefik/traefik/v2 2.11.43. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected >= 3.7.0-ea.1, < 3.7.0-rc.2; >= 3.0.0-beta1, < 3.6.14; fixed in 3.7.0-rc.2, 3.6.14
- Go github.com/traefik/traefik/v2: affected < 2.11.43; fixed in 2.11.43
- Go github.com/traefik/traefik: affected <= 1.7.34

## Suggested inspection (read-only)
- Go github.com/traefik/traefik/v3: check the installed version with your package manager.
- Go github.com/traefik/traefik/v2: check the installed version with your package manager.
- Go github.com/traefik/traefik: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/traefik/traefik/v3, github.com/traefik/traefik/v2, github.com/traefik/traefik.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6x2q-h3cr-8j2h (GitHub-reviewed advisory GHSA-6x2q-h3cr-8j2h lists affected ranges: Go github.com/traefik/traefik/v3 >=3.7.0-ea.1 =3.0.0-beta1 =0 =0 <=1.7.34)

Commands are suggestions: review each one before running it.

Loading voting…