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.
https://github.com/kumahq/kuma/security/advisories/GHSA-m58j-fjmc-h3g4
https://github.com/kumahq/kuma/pull/17463
https://github.com/kumahq/kuma/pull/17462
https://github.com/kumahq/kuma/pull/17461
https://github.com/kumahq/kuma/pull/17460
https://github.com/kumahq/kuma/pull/17459
https://github.com/kumahq/kuma/pull/17458
Published: 2026-08-17
Updated: 2026-08-17
Base Score: 5.5
Vector: CVSS2#AV:N/AC:L/Au:S/C:N/I:P/A:P
Severity: Medium
Base Score: 8.1
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Severity: High
Base 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
Severity: High