CVE-2026-41185 Affecting calico-3.29-pod2daemon-fips package, versions *


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.32% (24th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-CALICO329POD2DAEMONFIPS-17351213
  • published17 Jun 2026
  • disclosed28 May 2026

Introduced: 28 May 2026

NewCVE-2026-41185  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest calico-3.29-pod2daemon-fips.

NVD Description

Note: Versions mentioned in the description apply only to the upstream calico-3.29-pod2daemon-fips package and not the calico-3.29-pod2daemon-fips package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1