Homepage

Origin Validation Error Affecting kuma-2.13 package, versions <2.13.5-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.28% (21st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-KUMA213-18593791
  • published8 Aug 2026
  • disclosed28 May 2026
Report a new vulnerability Found a mistake?

Introduced: 28 May 2026

CVE-2026-45021  (opens in a new tab)
CWE-346  (opens in a new tab)
CWE-942  (opens in a new tab)

How to fix?

Upgrade Chainguard kuma-2.13 to version 2.13.5-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kuma-2.13 package and not the kuma-2.13 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.