CVE-2026-41184: Tigera Calico · Sensitive Data in Logs
Affects Tigera CalicoSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 28 May 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TigeraCalico | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict pods/log permissions in the calico-node namespace to trusted users only to limit token exposure via logs.
Description
CVE-2026-41184 is a vulnerability in Tigera Calico where the install-cni init container logs the rendered CNI configuration including a substituted Kubernetes ServiceAccount bearer token. This token is exposed in logs accessible to any authenticated user with pods/log permission in the calico-node namespace. The exposed token grants patch privileges on pods/status, enabling potential annotation-based attacks on cluster workloads. The default kubeconfig-based authentication is not affected. No patch or official remediation is currently confirmed.