cve.bz

CVE-2026-6720

7.2 highEPSS 0.2%

High (7.2). EPSS 0.2% chance of exploitation in the next 30 days. Fixed in github.com/projectcalico/calicoctl/v3 3.31.6.

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.

Severity

CVSS 4.0

7.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H
EPSS
0.2% chance of exploitation in the next 30 days; higher than 13% of CVEs (scores of 2026-10-31)
CWE
CWE-532
Published
Modified
Record from
the NVD, synced

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3m4q-ggcj-j6m4Gogithub.com/projectcalico/calicoctl/v3<3.31.63.31.6
GO-2026-5893Gogithub.com/projectcalico/calicoctlall versionsno fix published
GO-2026-5893Gogithub.com/projectcalico/calicoctl/v3all versionsno fix published

References

Check your stackJSON