| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/projectcalico/calico | ≥ 2.0.0, < 3.31.6< 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f | 3.31.61.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f |
| github.com/projectcalico/calico/v3 | all versions | |
| calico | ≥ 3.22.0, < 3.22.3< 22.4.0< 3.21.7< 3.32.0 | 3.22.322.4.03.21.73.32.0 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free