Kong Inc. Kong Mesh
Kong Mesh multi-zone: the global control plane attributes KDS-synced resources by an unvalidated in-band zone identifier
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.7.29
- >= 2.8.0, < 2.9.19
- >= 2.10.0, < 2.11.18
- >= 2.12.0, < 2.12.14
- >= 2.13.0, < 2.13.10
- >= 2.14.0, < 2.14.2
Fixed in 2.7.29, 2.9.19, 2.11.18, 2.12.14, 2.13.10, 2.14.2
Mitigation
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.
Workaround
Restrict which zones may enroll and protect zone tokens. No configuration flag disables the in-band attribution, so upgrading is the only fix.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.