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
nvd · CVE-2026-6720
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-532
Original publisher date fields
published: 2026-05-28T17:16:33.490
lastModified: 2026-06-17T11:01:12.887
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON