CVE-2026-6720

High

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.

SeverityHigh
CVSS7.2
Exploit probability—
ProductGithub.com/projectcalico/calicoctl/v3
PublishedMay 28, 2026
First seenMay 28, 2026
Weakness typeCWE-532CWE-532

How to fix

Affected products

ProductAffected versionsFixed in
github.com/projectcalico/calicoctl/v3Gov < 3.31.6, No range specified3.31.6
github.com/projectcalico/calicoctlGoNo range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2026-6720 · Github.com/projectcalico/calicoctl/v3 · Dark Radar