Description
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.
Published: 2026-08-12
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The readiness service of the Kong Mesh data plane exposes the Envoy admin API on TCP port 9902 without authentication. Attackers who can reach this port can read Envoy’s configuration files, cluster and listener lists, runtime statistics, and the mesh trust bundle, though they cannot perform destructive actions such as modifying the configuration. This oversight leads to a read‑only information disclosure vulnerability, allowing attackers to gain insight into the mesh topology and potentially use that knowledge for further attacks.

Affected Systems

Vendors and products impacted include Kong Inc. – Kong Mesh. Any installation of Kong Mesh running a data plane (kuma-dp) that uses the default Envoy admin API on a Unix domain socket and exposes the readiness service on port 9902 is affected; earlier versions than 2.14.2 are vulnerable, while 2.14.2 and later fix the issue by restricting the readiness reporter to only /ready and keeping the Envoy admin API bound exclusively to the Unix domain socket.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. The vulnerability can be exploited by any pod or entity with network reachability to port 9902, which is typically available within the cluster network. No authentication is required, and the attack path is straightforward local network access. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, but the threat is still meaningful due to the exposure of sensitive configuration data.

Generated by OpenCVE AI on August 13, 2026 at 00:35 UTC.

Remediation

Vendor Solution

Upgrade to Kong Mesh 2.14.2. In patched versions the readiness reporter serves only /ready; the Envoy admin API stays on the Unix domain socket, which is not reachable over the pod network.


Vendor Workaround

Restrict network access to port 9902 to trusted monitoring only, for example with a Kubernetes NetworkPolicy.


OpenCVE Recommended Actions

  • Upgrade to Kong Mesh 2.14.2 (or later) to ensure the readiness reporter exposes only the /ready endpoint and the Envoy admin API remains bound to the Unix domain socket.
  • Apply a Kubernetes NetworkPolicy that restricts access to port 9902 so that only trusted monitoring components can reach the service.
  • Reconfigure the data plane deployment to bind the readiness service to the loopback interface (127.0.0.1) instead of all interfaces, reducing the attack surface by preventing external pod access.

Generated by OpenCVE AI on August 13, 2026 at 00:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 13 Aug 2026 10:15:00 +0000

Type Values Removed Values Added
First Time appeared Konghq
Konghq kong Mesh
Vendors & Products Konghq
Konghq kong Mesh

Wed, 12 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Kong Mesh: the kuma-dp readiness service exposes the Envoy admin API without authentication
Weaknesses CWE-200
CWE-306
References
Metrics cvssV4_0

{'score': 5.3, 'vector': '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'}


Subscriptions

Konghq Kong Mesh
cve-icon MITRE

Status: PUBLISHED

Assigner: Kong

Published:

Updated: 2026-08-13T14:54:00.482Z

Reserved: 2026-08-03T15:18:30.454Z

Link: CVE-2026-18673

cve-icon Vulnrichment

Updated: 2026-08-13T14:53:55.492Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-08-12T19:17:30.480

Modified: 2026-08-31T19:22:43.473

Link: CVE-2026-18673

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T09:48:12Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-306

    Missing Authentication for Critical Function