CVE-2026-41184
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.
How to fix
- tigera calico3.21.7, 3.32.0, 22.4.0, 3.22.3 or later
- github.com/projectcalico/calico3.31.6, 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| tigera calico | v < 3.21.7, v < 3.32.0, v < 22.4.0, 3.22.0 ≤ v < 3.22.3 | 3.21.7, 3.32.0, 22.4.0, 3.22.3 |
| github.com/projectcalico/calicoGo | 2.0.0 ≤ v < 3.31.6, v < 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f | 3.31.6, 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f |
| github.com/projectcalico/calico/v3Go | No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.