CVE-2026-41184 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.5% (39th 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-17351327
  • published17 Jun 2026
  • disclosed28 May 2026

Introduced: 28 May 2026

NewCVE-2026-41184  (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.

In Calico, the install-cni init container logs the rendered CNI configuration to standard output. When the configuration template uses the SERVICEACCOUNT_TOKEN placeholder (Canal/Flannel-Calico deployments), the installer substitutes the live Kubernetes ServiceAccount bearer token before logging, exposing the token to any authenticated user with pods/log permission in the namespace with calico-node. The token holds patch privileges on pods/status, enabling annotation-based attacks against cluster workloads. The default kubeconfig-based authentication path is not affected. This is a direct regression of TTA-2018-001.

CVSS Base Scores

version 3.1