CVE-2026-41184
In Calico, the install-cni init container logs the rendered CNI …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/projectcalico/calico/pull/12502
- github.com/projectcalico/calico/pull/12526
- github.com/projectcalico/calico/pull/12527
- www.tigera.io/security-bulletins/tta-2026-001/
- nvd.nist.gov/vuln/detail/CVE-2026-41184
- www.tigera.io/security-bulletins/tta-2026-001
- github.com/projectcalico/calico/commit/0ca653db0ae7400ea9fb066daa7f45c902482271
- github.com/projectcalico/calico/commit/cd73bc2cea0f4989772f2deb93909e7cfac927e0
- nvd.nist.gov/vuln/detail/CVE-2026-41184
- cve.org/CVERecord?id=CVE-2026-41184
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.