ServiceAccount token disclosure via Azure IPAM CNI plugin logs
Tigera Calico · Tigera Calico Enterprise · Tigera Calico Cloud
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectcalico/calico Go |
|
|
| github.com/projectcalico/calico/v3 Go |
|
Tigera Calico · Tigera Calico Enterprise · Tigera Calico Cloud
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectcalico/calico Go |
|
|
| github.com/projectcalico/calico/v3 Go |
|
| No fix yet |
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.
From the CVE record · Tigera
When Calico uses the Azure IPAM plugin, its CNI binary logs the full configuration on every CNI ADD and DEL invocation. With token-based Kubernetes authentication, that log contains plaintext credentials; anyone with read access to the node’s CNI log can extract credentials that grant cluster-wide Calico networking admin privileges.
Operators of Tigera Calico, Calico Enterprise, or Calico Cloud using github.com/projectcalico/calico versions >=2.0.0 and <3.31.6 or before 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f, and users of github.com/projectcalico/calico/v3 at any version, should check their deployments.