EUVD-2026-57398
GHSA-jcrf-7pr5-jv5v
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Adjacent network access required (pod network); no auth needed; strictly read-only exposure so integrity and availability are unaffected.
Primary rating from Vendor (Kong).
CVSS VectorVendor: Kong
Lifecycle Timeline
2DescriptionCVE.org
When kuma-dp is configured with the Envoy admin API on a Unix domain socket, which is the default, its readiness service on TCP port 9902 - bound to all interfaces - forwards almost the entire Envoy admin API to any caller that can reach the port, with no authentication.
An attacker with network access to a data plane's port 9902, for example another pod on the cluster network, can read Envoy and data plane configuration without credentials: config dumps, cluster and listener lists, stats, and the mesh trust bundle. Exposure is read-only - destructive Envoy admin actions are blocked and private keys are not exposed.
AnalysisAI
Unauthenticated exposure of Envoy admin data in kuma-dp (Kong Mesh data plane) allows any pod on the Kubernetes cluster network to retrieve internal service mesh configuration without credentials. The readiness service on TCP port 9902, bound to all interfaces, acted as an unprotected reverse proxy forwarding nearly all Envoy admin read endpoints - including config dumps, cluster and listener lists, stats, and the mesh trust bundle - to any adjacent network caller. No public exploit code or CISA KEV listing exists at time of analysis; exploitation is bounded by the adjacent network prerequisite, but the risk is elevated in multi-tenant clusters where untrusted pods share the pod network.
Technical ContextAI
kuma-dp is the data plane sidecar component of Kuma and Kong Mesh, a CNCF-hosted service mesh built on Envoy proxy. Envoy's admin API is normally exposed on a Unix domain socket (UDS) to avoid network exposure - a deliberate security boundary. The readiness reporter component (app/kuma-dp/pkg/dataplane/readiness/component.go) was designed to proxy the /ready endpoint from the UDS to a TCP listener (port 9902) so that Kubernetes kubelet probes could reach it. However, the implementation also installed a catch-all reverse proxy handler (net/http/httputil.ReverseProxy) that forwarded all non-mutating Envoy admin endpoints over TCP. Only three paths were blocked (/quitquitquit, /drain_listeners, /runtime_modify); all read-only endpoints such as /config_dump, /clusters, /stats, /certs, and /logging were forwarded without authentication. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) accurately describes the root cause: a security boundary (UDS) was unintentionally bypassed by a proxy that bridged it to an open TCP port. The CPE cpe:2.3:a:kong_inc.:kong_mesh:*:*:*:*:*:*:*:* indicates all Kong Mesh versions are affected prior to the patch.
RemediationAI
Upgrade kuma-dp to the patched version incorporating the changes from GitHub PRs #17317 (https://github.com/kumahq/kuma/pull/17317) and #17418 (https://github.com/kumahq/kuma/pull/17418). The fix removes the Envoy admin reverse proxy handler entirely from the readiness reporter, restricting port 9902 to serve only the /ready endpoint; the Envoy admin API remains accessible exclusively over the Unix domain socket. The specific patched release version should be confirmed from the Kong Mesh changelog at https://developer.konghq.com/mesh/changelog/ before upgrading. As a compensating control pending upgrade, apply Kubernetes NetworkPolicy to each data plane pod namespace to allow inbound TCP connections on port 9902 only from the node's pod CIDR (required for kubelet liveness/readiness probes) and explicitly deny access from all other pods. Note: over-restricting NetworkPolicy may break kubelet health probes if the node IP range is not correctly allowed, so test in a staging environment before applying broadly.
Cross-zone isolation is broken in Kong Mesh's global control plane, allowing any authenticated zone to inject and overwr
SPIFFE identity impersonation in Kong Mesh universal mode allows an authenticated dataplane operator to assume another w
TLS certificate verification bypass in Kong Mesh's kuma-dp data plane component exposes authentication tokens to on-path
TLS certificate verification is silently disabled in the kumactl CLI (Kong Mesh / Kuma) when an operator registers an HT
Denial-of-service in Kong Mesh's kuma-cp control plane allows unauthenticated network-adjacent attackers to crash the en
Kong Mesh's control plane (kuma-cp) exposes the admin bootstrap token and JWT signing keys to any malicious webpage visi
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today