Vulnerability in github.com/projectcalico/calico (CVE-2026-41184)
Summary
Vulnerability in github.com/projectcalico/calico (CVE-2026-41184). Confidential information can be exposed externally. Mitigation: upgrade to 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f or later.
Original description
The description as published by the source.
In Calico, the install-cni init container logs the rendered CNI configuration to standard output. When the configuration template uses the SERVICEACCOUNT_TOKEN placeholder (Canal/Flannel-Calico deployments), the installer substitutes the live Kubernetes ServiceAccount bearer token before logging, exposing the token to any authenticated user with pods/log permission in the namespace with calico-node. The token holds patch privileges on pods/status, enabling annotation-based attacks against cluster workloads. The default kubeconfig-based authentication path is not affected. This is a direct regression of TTA-2018-001.
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-41184 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-41184" on the vendor's site.
CVE-2026-41184 (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.
A vulnerability (CWE-532) exists in github.com/projectcalico/calico.
Check the vendor advisory for the affected versions of github.com/projectcalico/calico.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f.
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/calico' . 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/calico' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/projectcalico/calicoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/projectcalico/calico to 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0fステージング環境で 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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