Read the docs
TI-2026-05888 Aliases CVE-2026-6720GHSA-3m4q-ggcj-j6m4

Calicoctl leaks cluster credentials to stderr when verbose logging is enabled

Priority LOW 31CWE-532Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Passive
Attack complexity
Low
Attack requirements
Present
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-532.

Summary

When calicoctl is invoked with --log-level=info or --log-level=debug, the client prints the full contents of its loaded connection-configuration struct to stderr in a single log line. The struct embeds every credential calicoctl uses to talk to the cluster — inline kubeconfig (with bearer token), Kubernetes API bearer token, etcd password, and inline PEM-encoded etcd client certificate and key. Any reader of that stderr stream — CI job logs, session-recording archives, shared support-ticket transcripts, or local filesystem viewers on the host that ran calicoctl — can extract these credentials with zero Kubernetes privilege. calicoctl's default log level is panic, so this issue only triggers when verbose logging is explicitly enabled.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00224 13th percentileScored 2026-11-07
Fix Fixed Calico (Tigera): 3.32.0Calico Enterprise (Tigera): 3.21.7, 3.22.3+2 more products

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
TigeraCalicobefore 3.32.03.32.0Patch availableCNA
TigeraCalico Enterprisebefore 3.21.73.21.7, 3.22.3Patch availableCNA
TigeraCalico Cloudbefore 22.4.022.4.0Patch availableCNA
—github.com/projectcalico/calicoctl/v3 (Go)before 3.31.63.31.6Patch availableGHSA-3m4q-ggcj-j6m4
  • Calico VendorTigera Affected before 3.32.0 Fixed in 3.32.0 Patch available CNA
  • Calico Enterprise VendorTigera Affected before 3.21.7 Fixed in 3.21.7, 3.22.3 Patch available CNA
  • Calico Cloud VendorTigera Affected before 22.4.0 Fixed in 22.4.0 Patch available CNA
  • github.com/projectcalico/calicoctl/v3 (Go) Vendor— Affected before 3.31.6 Fixed in 3.31.6 Patch available GHSA-3m4q-ggcj-j6m4

Remediation

  • Fix · CNA Calico (Tigera) Fixed in 3.32.0
  • Fix · CNA Calico Enterprise (Tigera) Fixed in 3.21.7, 3.22.3
  • Fix · CNA Calico Cloud (Tigera) Fixed in 22.4.0
  • Fix · GHSA-3m4q-ggcj-j6m4 github.com/projectcalico/calicoctl/v3 (Go) Fixed in 3.31.6 Advisory →

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Tigera Calico, Calico Cloud 22.4.0, 3.32.0

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-29808 ServiceAccount token disclosure via Azure IPAM CNI plugin logsPriority LOW 27

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-6720
  2. 2026-10-03 Alias added: GHSA-3m4q-ggcj-j6m4

References

  • TI-2023-21972 Calico Typha hangs during unclean TLS handshake CVSS 3.1HIGH 7.5
  • TI-2026-05735 L7 policy bypass via unnormalized HTTP path matching CVSS 4.0HIGH 7.9
  • TI-2024-22113 Privilege escalation in Calico CNI install binary CVSS 3.1MEDIUM 6.7
  • TI-2020-10675 Calico nodes IPv6 traffic redirection from route advertisment CVSS 3.1MEDIUM 6.0
  • TI-2026-29810 Calico Tier Authorization Bypass via DeleteCollection CVSS 4.0MEDIUM 6.2
  • TI-2026-29809 Unauthenticated Go pprof exposure in Calico debug server CVSS 4.0MEDIUM 6.0
See all 9 →

Sources