CVE-2026-114638: traefik · Improper Authentication
Affects traefikSource CVE Database V5
Not known to be exploited · CVSS 7.0 High : upgrade to 3.7.14 soon.
Data as of 26 Oct 2026, 14:18 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- 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-10-23.
- Patch
- Available – fixed in 3.7.14
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade traefik to 3.7.14.
Affected software
| Product | 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 3.7.14 or later, where this improper authentication vulnerability is fixed. No other mitigations are indicated by the vendor advisory.
Description
Traefik versions 3.7.0 through 3.7.13 have an improper authentication vulnerability in the Kubernetes Ingress NGINX provider. This flaw occurs due to merging client certificate authorities (CAs) when auth-tls-secret names collide after dot-to-dash normalization. As a result, attackers with certificates from a different host's CA can gain unauthorized access to hosts that require their own client CA, while legitimate clients of those hosts are denied access. The issue is fixed in version 3.7.14.