EUVD-2026-57424

In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane's kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane...

EUVD-2026-57423

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...

CVE-2026-18679

CVE-2026-18679 : Kong Mesh kuma-dp connects to the control plane over TLS without certificate verification when no CA is configured. This disables TLS peer verification for the data plane and sends the dataplane authentication token over the unverified channel. An on-path attacker can intercept t...

CVE-2026-18678

The CVE affects Kong Mesh/Kuma’s kumactl when adding an HTTPS control-plane profile without a CA certificate. The root cause is that kumactl disables TLS verification and sends API tokens over an unverified connection. This allows an attacker on the network path between the operator and the contr...

CVE-2026-18677

In Kong Mesh (universal mode), the XDS authenticator in kuma-cp validates the dataplane’s SPIFFE ID path template against the kuma.io/workload label only when the dataplane token is bound to a workload. Because workload binding is optional, a dataplane presenting a tags-bound token can register w...

CVE-2026-18676

The CVE-2026-18676 entry concerns Kong Mesh by exposing the admin bootstrap token and signing keys via a CORS misconfiguration in the default kuma-cp configuration. The vulnerability arises because a cross-origin fetch() from a malicious page can retrieve the admin JWT and signing material when t...

CVE-2026-18675

The vulnerability CVE-2026-18675 affects Kuma Kuma CP’s dataplane token validator, which uses an unchecked Go type assertion on the JWT kid header. If a token’s kid is a JSON number, it decodes as a float64 and triggers a runtime panic before signatures, claims, or authorization checks run. This ...