Home

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.

PUBLISHED Reserved 2026-04-20 | Published 2026-05-28 | Updated 2026-05-28 | Assigner Tigera




HIGH: 7.2CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H

Problem types

CWE-532

Product status

Default status
affected

Any version before 3.32.0
affected

Default status
affected

Any version before 3.21.7
affected

3.22.3 (semver)
unaffected

Default status
affected

Any version before 22.4.0
affected

Credits

Behnam Shobiri finder

Behnam Shobiri remediation developer

Anthony Tam remediation verifier

References

github.com/projectcalico/calico/pull/12535 patch

github.com/projectcalico/calico/pull/12536 patch

github.com/projectcalico/calico/pull/12537 patch

www.tigera.io/security-bulletins/tta-2026-003/ vendor-advisory

cve.org (CVE-2026-6720)

nvd.nist.gov (CVE-2026-6720)

Download JSON