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.
CVE-2026-6720
This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(medium)
- EPSS
- 13.0%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
May 29, 2026
Advisory Details (4)
Auto-updated Jun 11, 2026Security Bulletins – TTA-2026-003, CVE-2026-6720 | Tigera – Creator of Calico
https://www.tigera.io/security-bulletins/tta-2026-003/[release 3.31] Remove sensitive info from logs (pick 12535)
Fix merged in projectcalico/calico PR #12537 on 2026-04-20 — awaiting tagged release
https://github.com/projectcalico/calico/pull/12537[release 3.32] Remove sensitive info from logs (pick 12535)
Fix merged in projectcalico/calico PR #12536 on 2026-04-20 — awaiting tagged release
https://github.com/projectcalico/calico/pull/12536Sanitize calicoctl log output
Fix merged in projectcalico/calico PR #12535 on 2026-04-20 — awaiting tagged release
https://github.com/projectcalico/calico/pull/12535Vendor Advisories for CVE-2026-6720(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/projectcalico/calicoctl | — | — | — |
| github.com/projectcalico/calicoctl/v3 | — | 3.31.6 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 79× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 166 total refreshes for this CVE.
- 2026-07-16 02:55 UTCEG score recompute
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 19:52 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 18:08 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-02 12:59 UTCEG score recompute
- 2026-07-02 12:59 UTCGHSA enrichment
- 2026-07-01 15:30 UTCEG score recompute
- 2026-07-01 15:30 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 02:55 UTCEG score recompute
- 2026-07-01 02:55 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 02:07 UTCEG score recompute
- 2026-06-30 02:07 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:42 UTCEG score recompute
- 2026-06-29 13:42 UTCGHSA enrichment
- 2026-06-28 19:01 UTCEG score recompute
- 2026-06-28 19:01 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 06:37 UTCEG score recompute
- 2026-06-28 06:37 UTCGHSA enrichment
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 18:07 UTCEG score recompute
- 2026-06-27 18:07 UTCGHSA enrichment
- 2026-06-27 05:26 UTCEG score recompute
- 2026-06-27 05:26 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 16:47 UTCEG score recompute
- 2026-06-26 16:46 UTCGHSA enrichment
- 2026-06-25 20:29 UTCEG score recompute
- 2026-06-25 20:29 UTCGHSA enrichment
- 2026-06-25 13:50 UTCEPSS rescore
- 2026-06-25 08:04 UTCEG score recompute
- 2026-06-25 08:04 UTCGHSA enrichment
- 2026-06-24 16:38 UTCEG score recompute
- 2026-06-24 16:37 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 00:27 UTCEG score recompute
- 2026-06-19 00:26 UTCGHSA enrichment
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 18:04 UTCEG score recompute
- 2026-06-17 18:04 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 04:02 UTCEG score recompute
- 2026-06-17 04:02 UTCGHSA enrichment
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 15:38 UTCEG score recompute
- 2026-06-16 15:38 UTCGHSA enrichment
- 2026-06-16 01:20 UTCEG score recompute
- 2026-06-16 01:20 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 12:54 UTCEG score recompute
- 2026-06-15 12:54 UTCGHSA enrichment
- 2026-06-15 00:00 UTCEG score recompute
- 2026-06-14 23:59 UTCGHSA enrichment
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 11:36 UTCEG score recompute
- 2026-06-14 11:35 UTCGHSA enrichment
- 2026-06-13 23:12 UTCEG score recompute
- 2026-06-13 23:12 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 10:48 UTCEG score recompute
- 2026-06-13 10:48 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 22:23 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-17922EG 9.8CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS 94%CRITICAL
- CVE-2018-11716EG 9.8EPSS 96%CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8MEDIUM
- CVE-2018-1117NVD 5.0EG 9.8MEDIUM
- CVE-2018-11320EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-6720?
When was CVE-2026-6720 disclosed?
Is CVE-2026-6720 actively exploited?
What is the CVSS score of CVE-2026-6720?
How do I remediate CVE-2026-6720?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6720
Is Your Infrastructure Affected by CVE-2026-6720?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.