Skip to content

CVE-2026-6720 Calicoctl leaks cluster credentials to stderr when verbose logging is enabled

HighCVSS 7.2 EPSS 0.22%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial
Technology
Kubernetes

Description

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.

Upgrade path

4 packages: 3 fixed, 1 partially fixed.

PackageAffectedFixed inStatus
projectcalico github.com/projectcalico/calicoctl/v3(Go) < 3.31.6; All versions 3.31.6 Partially fixed
Tigera Calico < 3.32.0 3.32.0 Fixed
Tigera Calico Cloud < 22.4.0 22.4.0 Fixed
Tigera Calico Enterprise < 3.21.7 3.21.7 Fixed

Affected products

ProductAffected versionsFixed in
projectcalico github.com/projectcalico/calicoctl/v3(Go) < 3.31.6 3.31.6
projectcalico github.com/projectcalico/calicoctl/v3(Go) All versions No fix listed
Tigera Calico < 3.32.0 3.32.0
Tigera Calico Enterprise < 3.21.7 3.21.7
Tigera Calico Cloud < 22.4.0 22.4.0

References