Vulnerability in github.com/kumahq/kuma (CVE-2026-45021)
Summary
Vulnerability in github.com/kumahq/kuma (CVE-2026-45021). Risk of unauthorized operations or information disclosure. Exploitable via Origin. Mitigation: upgrade to 2.13.5 or later.
Original description
The description as published by the source.
Kuma is a modern Envoy-based service mesh that can run on every cloud across both Kubernetes and VMs. Prior to 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5, the default kuma-cp config leaks the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. CorsAllowedDomains: [".*"] reflects any Origin, and LocalhostIsAdmin: true promotes requests from 127.0.0.1 to mesh-system:admin. A cross-origin fetch() from a malicious page returns the admin JWT and signing material. This vulnerability is fixed in 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5.
Source: GitHub Security Advisories (Global) 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-45021 has been found in github.com/kumahq/kuma.
Attackers can target a specific entry point like Origin over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/kumahq/kuma to 2.13.5 or later.
If unsure, ask your IT team or search "github.com/kumahq/kuma CVE-2026-45021" on the vendor's site.
CVE-2026-45021 (github.com/kumahq/kuma) — CWE-346
Attack surface: Origin / KUMA_API_SERVER_CORS_ALLOWED_DOMAINS / CorsAllowedDomains / LocalhostIsAdmin
Patched: 2.13.5 — 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-346) exists in github.com/kumahq/kuma. Attackers reach the vulnerable code path via Origin.
Check the vendor advisory for the affected versions of github.com/kumahq/kuma. Attack surface: Origin / KUMA_API_SERVER_CORS_ALLOWED_DOMAINS / CorsAllowedDomains / LocalhostIsAdmin.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.13.5.
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/kumahq/kuma' . 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/kumahq/kuma' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/kumahq/kumaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/kumahq/kuma to 2.13.5ステージング環境で 2.13.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com