GHSA-9p7w-w5q6-mxj3 Calico Inserts Sensitive Information into Log File

• Go github.com/projectcalico/calico: >= 2.0.0, < 3.31.6 → fixed in 3.31.6 • Go github.com/projectcalico/calico: < 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f → fixed in 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f

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.