When calicoctl is invoked with --log-level=info or --log-level=debug, the client prints the full contents of…
Historical advisory recorded 25 Oct 2026 15:18:51 UTC. Read the latest advisory.
nvd · CVE-2026-6720
PublishedWhen 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-6720 · CVE overview and exploitation status
nvd · CVE-2026-6720
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.