Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The Go package github.com/projectcalico/calicoctl/v3 is affected in versions before 3.31.6. When calicoctl runs with --log-level set to info or debug, it writes its full connection configuration, including credentials such as bearer tokens, the etcd password, and etcd client certificate and key, to stderr. Anyone who can read that output, such as CI logs or shared transcripts, can obtain those credentials without Kubernetes privileges. Upgrade to version 3.31.6. Avoiding verbose log levels also prevents the exposure, since the default level is panic.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.2 | High | 4.0 | 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 | CNA (Tigera) |
- CISA KEV Not listed.
- EPSS 0.0022, the 13th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-3m4q-ggcj-j6m4
- OSV: GHSA-3m4q-ggcj-j6m4
- nvd.nist.gov/vuln/detail/CVE-2026-6720
- github.com/projectcalico/calico/pull/12535
- github.com/projectcalico/calico/pull/12536
- github.com/projectcalico/calico/pull/12537
- github.com/projectcalico/calico/commit/12908bb48a5bf8cbab5373f4d532509a30cf9b7f
- github.com/projectcalico/calico/commit/8d87eddcb5eb6efc70c09eb0a33d63137359ea70
- github.com/projectcalico/calico/commit/ce3ab2b39b5841757cbccf7922c895c47827f562
- github.com/projectcalico/calico
- www.tigera.io/security-bulletins/tta-2026-003