CVE-2026-85597: traefik · Incorrect Authorization
Affects traefikSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 2.11.55 soon.
Data as of 20 Nov 2026, 14:49 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.2 |
|---|
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-04.
- Patch
- Available – fixed in 2.11.55, 3.7.11
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade traefik to 2.11.55; traefik to 3.7.11; traefik to 3.7.11 or 2.11.55.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| traefiktraefik | Affected
| Fixed in
|
| traefiktraefik | Affected
| Fixed in
|
Gotraefikpkg:golang/traefikOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Traefik to version 2.11.55 or later, or 3.7.11 or later, where this vulnerability has been fixed. No other mitigation is required as the fix is available in these official releases.
Description
Traefik versions before 2.11.55 and 3.7.11 contain a vulnerability in TLS option conflict resolution that allows unauthenticated attackers to bypass client-certificate authentication. This occurs when conflicting TLS options are configured on multi-host routers, enabling attackers to access protected backends by exploiting shared TLS resolution across multiple hostnames in a single router rule.