CVE-2026-18673
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
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Kong Inc. | Kong Mesh | 2.14.0 < 2.14.2 | affected |
Weaknesses
- CWE-200: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- CWE-306: CWE-306 Missing Authentication for Critical Function
Workarounds
Restrict network access to port 9902 to trusted monitoring only, for example with a Kubernetes NetworkPolicy.
References
- https://github.com/kumahq/kuma/security/advisories/GHSA-r9pv-x3pm-4r2w
- https://github.com/kumahq/kuma/pull/17317
- https://github.com/kumahq/kuma/pull/17418
- https://developer.konghq.com/mesh/changelog/
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.