When Calico is configured with the Azure IPAM plugin, the Calico CNI binary mutates the incoming CNI…
Historical advisory recorded 25 Oct 2026 09:17:30 UTC. Read the latest advisory.
nvd · CVE-2026-41185
PublishedWhen 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.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2026-41185
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-532
Original publisher date fields
published: 2026-05-28T17:16:22.670
lastModified: 2026-06-17T10:46:17.790
3 source CPE criteria · context only
- cpe:2.3:a:tigera:calico:*:*:*:*:enterprise:*:*:*
- cpe:2.3:a:tigera:calico:*:*:*:*:open_source:*:*:*
- cpe:2.3:a:tigera:calico:*:*:*:*:cloud:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON