CVE-2026-41185

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.

CVE-2026-41185 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.31.6, 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41185? CVE-2026-41185 is a medium-severity security vulnerability in github.com/projectcalico/calico (go), affecting versions >= 2.0.0, < 3.31.6. It is fixed in 3.31.6, 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f.
2. How severe is CVE-2026-41185? CVE-2026-41185 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/projectcalico/calico are affected by CVE-2026-41185? github.com/projectcalico/calico (go) versions >= 2.0.0, < 3.31.6 is affected.
4. Is there a fix for CVE-2026-41185? Yes. CVE-2026-41185 is fixed in 3.31.6, 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f. Upgrade to this version or later.
5. Is CVE-2026-41185 exploitable, and should I be worried? Whether CVE-2026-41185 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41185 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41185?
   • Upgrade github.com/projectcalico/calico to 3.31.6 or later
   • Upgrade github.com/projectcalico/calico to 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f or later