GHSA-9p7w-w5q6-mxj3
Calico Inserts Sensitive Information into Log File
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Go | github.com/projectcalico/calico | >= 2.0.0, < 3.31.6 | 3.31.6 |
| Go | github.com/projectcalico/calico | < 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f | 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f |
Details
As written in the advisory (Markdown source, shown as plain text).
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
External links from the advisory. They lead to third-party sites.
- https://nvd.nist.gov/vuln/detail/CVE-2026-41184
- https://github.com/projectcalico/calico/pull/12502
- https://github.com/projectcalico/calico/pull/12526
- https://github.com/projectcalico/calico/pull/12527
- https://github.com/projectcalico/calico/commit/0ca653db0ae7400ea9fb066daa7f45c902482271
- https://github.com/projectcalico/calico/commit/cd73bc2cea0f4989772f2deb93909e7cfac927e0
- https://github.com/projectcalico/calico/commit/da9ea3a13927a35e4022b787d17a005b2157d812
- https://github.com/projectcalico/calico
- https://www.tigera.io/security-bulletins/tta-2026-001