CVE-2026-6720
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
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Tigera | Calico | 0 < 3.32.0 | affected |
| Tigera | Calico Enterprise | 0 < 3.21.7 | affected |
| Tigera | Calico Enterprise | 3.22.3 | unaffected |
| Tigera | Calico Cloud | 0 < 22.4.0 | affected |
Weaknesses
- CWE-532: CWE-532
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: no
- Technical Impact: partial
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/
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.