← console
voxell vciy

CVE-2026-65600: Traefik before v2.11.52 Authentication Bypass via ReplacePathRegex

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: 2.11.52; 3.6.23; 3.7.7 CVE record
  2. Later advisories still cover the fixes above and name higher ones: github.com/traefik/traefik/v2 2.11.53 (CVE-2026-71324), 2.11.54 (CVE-2026-71325), 2.11.56 (CVE-2026-88011), 2.11.56 (CVE-2026-88012), 2.11.56 (CVE-2026-88878), 2.11.56 (CVE-2026-88879), 2.11.57 (CVE-2026-88007), 2.11.57 (CVE-2026-88008), 2.11.57 (CVE-2026-88009) OSV advisories
  3. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  4. Check your version against the ranges this record publishes.

What it is stated by the CNA

Traefik versions <= v2.11.51, >= v3.6.0 <= v3.6.22, and >= v3.7.0 <= v3.7.6 contain an authentication bypass via path traversal in the ReplacePathRegex middleware. When ReplacePathRegex is configured with a regex that captures user-controlled path segments without a mandatory path separator (e.g. regex "^/api(.*)", replacement "/$1"), the middleware forwards the replaced path to the backend without validating that it matches its normalized form. An unauthenticated remote attacker can send a crafted request (e.g. GET /api../admin) that produces an un-normalized path such as /../admin, which a backend that normalizes paths resolves to a protected route, bypassing authentication middleware. Fixed in v2.11.52, v3.6.23, and v3.7.7.

weakness
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
affected
traefik
published ranges
traefik < 2.11.52; traefik >= 3.6.0 < 3.6.23; traefik >= 3.7.0 < 3.7.7
fixed in
2.11.52; 3.6.23; 3.7.7
fixed by package (from OSV advisories)
github.com/traefik/traefik/v2 (Go): 2.11.52 GHSA-cxjq-mrr5-89rv GO-2026-6208github.com/traefik/traefik/v3 (Go): 3.6.23; 3.7.7 GHSA-cxjq-mrr5-89rv GO-2026-6208
later fixes (from OSV advisories)
github.com/traefik/traefik/v2 2.11.52 is inside a range CVE-2026-71324 (GHSA-3ccp-42pg-hgv6) lists as affected. That advisory is fixed in 2.11.53.github.com/traefik/traefik/v2 2.11.52 is inside a range CVE-2026-71325 (GHSA-62fc-8686-hfmq) lists as affected. That advisory is fixed in 2.11.54.github.com/traefik/traefik/v2 2.11.52 is inside a range CVE-2026-88007 (GHSA-qqjf-53cj-pwvv) lists as affected. That advisory is fixed in 2.11.57.github.com/traefik/traefik/v2 2.11.52 is inside a range CVE-2026-88008 (GHSA-w4v4-9rw7-5326) lists as affected. That advisory is fixed in 2.11.57.github.com/traefik/traefik/v2 2.11.52 is inside a range CVE-2026-88009 (GHSA-f52w-8j3h-j724) lists as affected. That advisory is fixed in 2.11.57.github.com/traefik/traefik/v2 2.11.52 is inside a range CVE-2026-88011 (GHSA-rf44-j88r-hh8c) lists as affected. That advisory is fixed in 2.11.56.
severity
7.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
assigned by
VulnCheck
published
2026-07-22

check us github.com vulncheck.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
23 Jul 20260.01041
24 Jul 20260.00674
7 Aug 20260.0041
28 Aug 20260.00412
28 Sep 20260.00621

5 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: 2.11.52; 3.6.23; 3.7.7. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-65600', '2026-10-31T23:59:59.999999Z', now());