Vulnerability Description
In Calico, the install-cni init container logs the rendered CNI configuration to standard output. When the configuration template uses the __SERVICEACCOUNT_TOKEN__ placeholder (Canal/Flannel-Calico deployments), the installer substitutes the live Kubernetes ServiceAccount bearer token before logging, exposing the token to any authenticated user with pods/log permission in the namespace with calico-node. The token holds patch privileges on pods/status, enabling annotation-based attacks against cluster workloads. The default kubeconfig-based authentication path is not affected. This is a direct regression of TTA-2018-001.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tigera | Calico | < 3.21.7 |
Related Weaknesses (CWE)
References
- https://github.com/projectcalico/calico/pull/12502Issue TrackingPatch
- https://github.com/projectcalico/calico/pull/12526Issue TrackingPatch
- https://github.com/projectcalico/calico/pull/12527Issue TrackingPatch
- https://www.tigera.io/security-bulletins/tta-2026-001/MitigationVendor Advisory
FAQ
What is CVE-2026-41184?
CVE-2026-41184 is a vulnerability with a CVSS score of 6.5 (MEDIUM). In Calico, the install-cni init container logs the rendered CNI configuration to standard output. When the configuration template uses the __SERVICEACCOUNT_TOKEN__ placeholder (Canal/Flannel-Calico de...
How severe is CVE-2026-41184?
CVE-2026-41184 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-41184?
Check the references section above for vendor advisories and patch information. Affected products include: Tigera Calico.