CVE-2026-41184: Calico Inserts Sensitive Information into Log File
(updated )
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.
References
- github.com/advisories/GHSA-9p7w-w5q6-mxj3
- github.com/projectcalico/calico/commit/0ca653db0ae7400ea9fb066daa7f45c902482271
- github.com/projectcalico/calico/commit/cd73bc2cea0f4989772f2deb93909e7cfac927e0
- github.com/projectcalico/calico/commit/da9ea3a13927a35e4022b787d17a005b2157d812
- github.com/projectcalico/calico/pull/12502
- github.com/projectcalico/calico/pull/12526
- github.com/projectcalico/calico/pull/12527
- nvd.nist.gov/vuln/detail/CVE-2026-41184
- www.tigera.io/security-bulletins/tta-2026-001
Code Behaviors & Features
Detect and mitigate CVE-2026-41184 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →