Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41184: In Calico, the install-cni init container logs the rendered CNI configuration to standard output

33
Routine
MEDIUM 6.5UPGRADE

CVE-2026-41184 is a medium-severity flaw (CVSS 6.5) affecting calico. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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/st

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.5% (top 57%)
CISA exploited listNo
WeaknessCWE-532
Published2026-05-28
Last modified2026-10-26
Publisher (CNA): Tigera, Inc. · Vendor: tigera

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

tigera calico UPGRADE
Affected: < 3.21.7 · < 3.32.0 · < 22.4.0 · >= 3.22.0 and < 3.22.3
Fixed in: 3.21.7, 3.22.3, 3.32.0, 22.4.0
Safe to downgrade to: a release before 3.22.0
1. Check installed version
apt-cache policy calico || rpm -q calico || calico --version
2. UPGRADE to 3.21.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade calico
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade calico
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.22.0 (Debian / Ubuntu)
apt-cache madison calico sudo apt install calico=<VERSION_BEFORE_3.22.0> sudo apt-mark hold calico
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list calico sudo dnf downgrade calico-<VERSION_BEFORE_3.22.0> sudo dnf versionlock add calico
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41184?

calico: upgrade to 3.21.7, 3.22.3, 3.32.0, 22.4.0. Exact commands for each OS are on this page.

Is CVE-2026-41184 being exploited?

CVE-2026-41184 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41184 affect?

CVE-2026-41184 affects calico. Severity is medium (CVSS 6.5). 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 th

How urgent is CVE-2026-41184?

Priority 33/100. No elevated risk signals yet.

Software pages

Kubernetes vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.