CVE-2026-6720
Fixed in a distro release EPSS <1%CVSS 7.2
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.
Products: tigera calico, Tigera Calico Enterprise, Tigera Calico Cloud
Fixed upstream
| Ecosystem | Package | Fixed in |
|---|---|---|
| Go | github.com/projectcalico/calicoctl | no fix |
| Go | github.com/projectcalico/calicoctl/v3 | 3.31.6 |
| Go | github.com/projectcalico/calicoctl/v3 | no fix |
Distro releases
| Release | Package | Fixed in |
|---|---|---|
| Chainguard | calico-cni-fips-3.31 | 0 |
| openSUSE Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 |