Skip to main content
VulnerabilityPublished

CVE-2026-41185: Tigera Calico · Sensitive Data in Logs

Affects Tigera CalicoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium · patch available : update Tigera Calico when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
TigeraCalicoAffected
  • <3.32.0
Fixed in–
TigeraCalico EnterpriseAffected
  • <3.21.7
  • >=3.22.0 <3.22.3
Fixed in–
TigeraCalico CloudAffected
  • <22.4.0
Fixed in–

AI-suggested

The vendor manages remediation for this cloud-hosted service. A patch is available, and users should consult the vendor advisory for current remediation guidance. Since this is a cloud service, the vendor typically applies fixes server-side. Users should verify with Tigera that their environment has been updated to prevent sensitive information from being logged.

Description

A vulnerability in Tigera Calico occurs when configured with the Azure IPAM plugin. The Calico CNI binary modifies the CNI configuration to add subnet information and then logs the entire configuration, including sensitive Kubernetes authentication tokens, at INFO level to a local log file on each pod addition or deletion. This exposes ServiceAccount tokens and related credentials in plaintext to any user with read access to the log file, potentially granting cluster-wide Calico networking admin privileges.

References

Community reviews

Loading reviews…