← Back
CVE-2026-41185
medium
CVSS 6.5
Vulnerability in github.com/projectcalico/calico (CVE-2026-41185)
Summary
vulnerability in github.com/projectcalico/calico (CVE-2026-41185). Confidential information can be exposed externally. Mitigation: upgrade to `1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41185** has been found in github.com/projectcalico/calico.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade github.com/projectcalico/calico to **1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f** or later.
If unsure, ask your IT team or search "github.com/projectcalico/calico CVE-2026-41185" on the vendor's site.
CVE-2026-41185 (github.com/projectcalico/calico) — CWE-532 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: `1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f` — 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/calico.
📍 Affected scope
github.com/projectcalico/calico — .
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f**.
🛡️ 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/calico' .` 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/calico' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/projectcalico/calico` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/projectcalico/calico to 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0fステージング環境で 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/projectcalico/calico
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f"}]}]
References
- patch [email protected]
- web https://github.com/projectcalico/calico/pull/12502
- web https://github.com/projectcalico/calico/pull/12526
- web https://github.com/projectcalico/calico/pull/12527
- web https://nvd.nist.gov/vuln/detail/CVE-2026-41185
- web https://www.tigera.io/security-bulletins/tta-2026-002
- web https://github.com/advisories/GHSA-m67g-87rx-v42c
- web https://github.com/projectcalico/calico/commit/0ca653db0ae7400ea9fb066daa7f45c902482271
- web https://github.com/projectcalico/calico/commit/cd73bc2cea0f4989772f2deb93909e7cfac927e0
- web https://github.com/projectcalico/calico/commit/da9ea3a13927a35e4022b787d17a005b2157d812