Vulnerability in github.com/projectcalico/calicoctl/v3 (CVE-2026-6720)
Summary
Vulnerability in github.com/projectcalico/calicoctl/v3 (CVE-2026-6720). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.31.6 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-6720 has been found in github.com/projectcalico/calicoctl/v3.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/projectcalico/calicoctl/v3 to 3.31.6 or later.
If unsure, ask your IT team or search "github.com/projectcalico/calicoctl/v3 CVE-2026-6720" on the vendor's site.
CVE-2026-6720 (github.com/projectcalico/calicoctl/v3) — CWE-532
Patched: 3.31.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-532) exists in github.com/projectcalico/calicoctl/v3.
Check the vendor advisory for the affected versions of github.com/projectcalico/calicoctl/v3.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.31.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/projectcalico/calicoctl/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/projectcalico/calicoctl/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/projectcalico/calicoctl/v3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/projectcalico/calicoctl/v3 to 3.31.6ステージング環境で 3.31.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory tigera.io
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- web tigera.io
- web github.com
- web github.com
- web github.com