Description
On a Kong Mesh global control plane, resources received over the zone-to-global KDS sync are attributed using the in-band, sender-controlled ControlPlane.Identifier rather than the authenticated zone identity derived from the connection. Authenticated zones can have the global control plane store and re-distribute those resources as belonging to another zone.



The result is a cross-zone isolation bypass: the holder of a single enrolled zone's credential can inject, attribute, and overwrite resources in another zone's namespace mesh-wide.




The root cause lives in Kuma's open-source KDS sync code, which Kong Mesh's control plane is built on.
Published: 2026-08-17
Score: 7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability occurs on a Kong Mesh global control plane where resources received over the zone‑to‑global KDS sync are attributed to the in‑band, sender‑controlled ControlPlane.Identifier instead of the authenticated zone identity derived from the connection. An attacker who owns the credentials of any enrolled zone can therefore inject, attribute, and overwrite resources in another zone’s namespace, effectively bypassing cross‑zone isolation and enabling unauthorized resource manipulation across the mesh. This is rooted in improper authorization logic (CWE‑863) and related to ineffective validation of input (CWE‑345).

Affected Systems

The affected product is Kong Mesh from Kong Inc. All versions prior to the following patched releases are impacted: 2.7.29, 2.9.19, 2.11.18, 2.12.14, 2.13.10, and 2.14.2. Any deployment using Kong Mesh without upgrading to one of these versions remains vulnerable.

Risk and Exploitability

The CVSS score of 7 indicates high severity, and while the EPSS score is not available, the lack of KEV listing means the vulnerability has not yet been confirmed as actively exploited in the wild. Exploitation requires an authenticated zone credential and access to the zone‑to‑global KDS sync endpoint, which many internal or network‑perimeter users possess. Because the attacker can supply the in‑band ControlPlane.Identifier arbitrarily, the attack can be performed over the network without privilege escalation, allowing widespread injection and overwrite of resources inside any target zone. Consequently the risk profile is high and the vulnerability should be remediated promptly.

Generated by OpenCVE AI on August 17, 2026 at 13:30 UTC.

Remediation

Vendor Solution

Upgrade to Kong Mesh 2.7.29, 2.9.19, 2.11.18, 2.12.14, 2.13.10 or 2.14.2, whichever matches your release line. In patched versions the global KDS ingest path attributes synced resources by the authenticated connection identity instead of the in-band field.


Vendor Workaround

Restrict which zones may enroll and protect zone tokens. No configuration flag disables the in-band attribution, so upgrading is the only fix.


OpenCVE Recommended Actions

  • Upgrade Kong Mesh to one of the patched releases (2.7.29, 2.9.19, 2.11.18, 2.12.14, 2.13.10, or 2.14.2) to ensure the control plane uses the authenticated connection identity for resource attribution.
  • If an immediate upgrade is not possible, restrict zone enrollment so that only trusted parties can enroll zones and protect zone tokens, thereby limiting the potential for a malicious zone to inject resources.
  • Continuously monitor KDS sync traffic for unexpected ControlPlane.Identifier values and enforce strict validation of zone identifiers to detect and prevent unauthorized resource injection attempts.

Generated by OpenCVE AI on August 17, 2026 at 13:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 21 Aug 2026 21:45:00 +0000

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

Mon, 17 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'}


Mon, 17 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
Description On a Kong Mesh global control plane, resources received over the zone-to-global KDS sync are attributed using the in-band, sender-controlled ControlPlane.Identifier rather than the authenticated zone identity derived from the connection. Authenticated zones can have the global control plane store and re-distribute those resources as belonging to another zone. The result is a cross-zone isolation bypass: the holder of a single enrolled zone's credential can inject, attribute, and overwrite resources in another zone's namespace mesh-wide. The root cause lives in Kuma's open-source KDS sync code, which Kong Mesh's control plane is built on.
Title Kong Mesh multi-zone: the global control plane attributes KDS-synced resources by an unvalidated in-band zone identifier
Weaknesses CWE-345
CWE-863
References
Metrics cvssV4_0

{'score': 7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:L/SI:L/SA:N'}


Subscriptions

Konghq Kong Mesh
cve-icon MITRE

Status: PUBLISHED

Assigner: Kong

Published:

Updated: 2026-08-17T14:46:48.378Z

Reserved: 2026-08-03T15:20:40.972Z

Link: CVE-2026-18674

cve-icon Vulnrichment

Updated: 2026-08-17T14:46:42.858Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-08-17T13:16:51.820

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

Link: CVE-2026-18674

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T21:19:44Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-863

    Incorrect Authorization