GHSA-m67g-87rx-v42c 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

When Calico is configured with the Azure IPAM plugin, the Calico CNI binary mutates the incoming CNI configuration to attach subnet information before delegating to the IPAM plugin. After mutating, the Azure IPAM helper logs the entire unmarshaled configuration map (stdinData) at INFO level to /var/log/calico/cni/cni.log on every CNI ADD and DEL invocation — once per pod scheduled or terminated on the node. When the cluster is deployed using token-based Kubernetes authentication, this log entry contains the ServiceAccount token, client key, and certificate authority in plaintext. Any principal with read access to /var/log/calico/cni/cni.log on a node  can read these logs and extract the credentials, which grant cluster-wide Calico networking admin privileges.