Kong Mesh: default control plane config leaks the admin token cross-origin via a CORS wildcard and localhost admin
The default kuma-cp configuration in Kong Mesh reveals the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. Due to a CORS misconfiguration a cross-origin fetch() from a malicious page returns the admin JWT and signing material.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-45021US | — | — | ||
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 con… | ||||
02
references
External citations — patches, advisories, analysis.
- https://developer.konghq.com/mesh/changelog/ADVISORY
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/18xxx/CVE-2026-18676.jsonADVISORY
- https://github.com/kumahq/kuma/pull/16416FIX
- https://github.com/kumahq/kuma/pull/16423FIX
- https://github.com/kumahq/kuma/pull/16424FIX
- https://github.com/kumahq/kuma/pull/16425FIX
- https://github.com/kumahq/kuma/pull/16426FIX
- https://github.com/kumahq/kuma/pull/16427FIX
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan