Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/projectcalico/calico/pull/12535
- https://github.com/projectcalico/calico/pull/12536
- https://github.com/projectcalico/calico/pull/12537
- https://www.tigera.io/security-bulletins/tta-2026-003/
FAQ
What is CVE-2026-6720?
CVE-2026-6720 is a documented vulnerability. 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 embed...
How severe is CVE-2026-6720?
CVSS scoring is not yet available for CVE-2026-6720. Check NVD for updates.
Is there a patch for CVE-2026-6720?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.