CVE-2026-6720

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

May 28, 2026

Last Modified

May 29, 2026

Advisory Details (4)

Auto-updated Jun 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

Security Bulletins – TTA-2026-003, CVE-2026-6720 | Tigera – Creator of Calico

https://www.tigera.io/security-bulletins/tta-2026-003/
github_pr

[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
github_pr

[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/12536
github_pr

Sanitize calicoctl log output

Fix merged in projectcalico/calico PR #12535 on 2026-04-20 — awaiting tagged release

https://github.com/projectcalico/calico/pull/12535

Vendor 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)
PackageVulnerable rangeFixed inDependents
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 6× in last 7d / 41× 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 190 total refreshes for this CVE.

  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-26 14:47 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:44 UTCEG score recompute
  11. 2026-08-23 14:29 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 00:40 UTCEG score recompute
  15. 2026-08-20 22:56 UTCEPSS rescore
  16. 2026-08-20 10:46 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:49 UTCEPSS rescore
  19. 2026-08-18 13:49 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 15:10 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:34 UTCEG score recompute
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 01:47 UTCEG score recompute
  2. 2026-08-15 01:31 UTCEPSS rescore
  3. 2026-08-14 01:00 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 14:16 UTCEG score recompute
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-12 01:52 UTCEG score recompute
  8. 2026-08-11 01:04 UTCEG score recompute
  9. 2026-08-11 00:00 UTCEPSS rescore
  10. 2026-08-10 00:16 UTCEG score recompute
  11. 2026-08-09 13:47 UTCEPSS rescore
  12. 2026-08-08 23:11 UTCEG score recompute
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-07 22:24 UTCEG score recompute
  15. 2026-08-06 21:37 UTCEG score recompute
  16. 2026-08-06 13:47 UTCEPSS rescore
  17. 2026-08-05 20:48 UTCEG score recompute
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-04 23:43 UTCEG score recompute
  21. 2026-08-04 15:10 UTCEPSS rescore
  22. 2026-08-04 10:39 UTCEPSS rescore
  23. 2026-08-03 16:11 UTCEG score recompute
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-02 02:56 UTCEG score recompute
  26. 2026-08-02 02:27 UTCEPSS rescore
  27. 2026-07-31 06:20 UTCEG score recompute
  28. 2026-07-30 16:28 UTCEPSS rescore
  29. 2026-07-30 01:30 UTCEPSS rescore
  30. 2026-07-29 14:16 UTCEG score recompute
  31. 2026-07-28 15:37 UTCEPSS rescore
  32. 2026-07-27 14:14 UTCEPSS rescore
  33. 2026-07-27 09:40 UTCEG score recompute
  34. 2026-07-26 14:54 UTCEPSS rescore
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-24 14:18 UTCEPSS rescore
  37. 2026-07-24 14:18 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 03:22 UTCEG score recompute
  41. 2026-07-22 14:08 UTCEPSS rescore
  42. 2026-07-22 14:08 UTCEPSS rescore
  43. 2026-07-21 15:25 UTCEPSS rescore
  44. 2026-07-21 15:25 UTCEPSS rescore
  45. 2026-07-20 17:08 UTCEPSS rescore
  46. 2026-07-19 14:31 UTCEPSS rescore
  47. 2026-07-19 02:29 UTCEPSS rescore
  48. 2026-07-18 10:04 UTCEPSS rescore
  49. 2026-07-16 17:03 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 02:00 UTCEPSS rescore
  52. 2026-07-13 22:31 UTCEPSS rescore
  53. 2026-07-13 06:13 UTCEPSS rescore
  54. 2026-07-13 06:13 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-09 19:10 UTCEPSS rescore
  59. 2026-07-09 19:10 UTCEPSS rescore
  60. 2026-07-08 15:16 UTCEPSS rescore
  61. 2026-07-08 15:16 UTCEPSS rescore
  62. 2026-07-07 13:46 UTCEPSS rescore
  63. 2026-07-07 13:46 UTCEPSS rescore
  64. 2026-07-06 16:27 UTCEPSS rescore
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-06 02:23 UTCEPSS rescore
  68. 2026-07-05 02:31 UTCEPSS rescore
  69. 2026-07-05 02:30 UTCEPSS rescore
  70. 2026-07-04 06:31 UTCEPSS rescore
  71. 2026-07-04 06:31 UTCEPSS rescore
  72. 2026-07-02 12:59 UTCGHSA enrichment
  73. 2026-07-01 15:30 UTCGHSA enrichment
  74. 2026-07-01 15:07 UTCEPSS rescore
  75. 2026-07-01 02:55 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-6720?
CVE-2026-6720 is a high vulnerability published on May 28, 2026. 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),…
When was CVE-2026-6720 disclosed?
CVE-2026-6720 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6720 actively exploited?
CVE-2026-6720 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.1% of all scored CVEs.
What is the CVSS score of CVE-2026-6720?
CVE-2026-6720 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-6720?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6720, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6720

Explore →

Is Your Infrastructure Affected by CVE-2026-6720?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs