← Back
CVE-2026-6720
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.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-6720** has been found in github.com/projectcalico/calicoctl/v3.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-532) exists in github.com/projectcalico/calicoctl/v3.
📍 Affected scope
github.com/projectcalico/calicoctl/v3 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.31.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/projectcalico/calicoctl/v3 to 3.31.6ステージング環境で 3.31.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/projectcalico/calicoctl/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.31.6"}]}]
References
- web https://github.com/projectcalico/calico/pull/12535
- web https://github.com/projectcalico/calico/pull/12536
- web https://github.com/projectcalico/calico/pull/12537
- web [email protected]
- web https://nvd.nist.gov/vuln/detail/CVE-2026-6720
- web https://www.tigera.io/security-bulletins/tta-2026-003
- web https://github.com/advisories/GHSA-3m4q-ggcj-j6m4
- web https://github.com/projectcalico/calico/commit/12908bb48a5bf8cbab5373f4d532509a30cf9b7f
- web https://github.com/projectcalico/calico/commit/8d87eddcb5eb6efc70c09eb0a33d63137359ea70
- web https://github.com/projectcalico/calico/commit/ce3ab2b39b5841757cbccf7922c895c47827f562