Vulnerability 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.
Related Weaknesses (CWE)
References
- https://developer.konghq.com/mesh/changelog/
- https://github.com/kumahq/kuma/pull/17456
- https://github.com/kumahq/kuma/pull/17458
- https://github.com/kumahq/kuma/pull/17459
- https://github.com/kumahq/kuma/pull/17460
- https://github.com/kumahq/kuma/pull/17461
- https://github.com/kumahq/kuma/pull/17462
- https://github.com/kumahq/kuma/pull/17463
- https://github.com/kumahq/kuma/security/advisories/GHSA-m58j-fjmc-h3g4
FAQ
What is CVE-2026-18674?
CVE-2026-18674 is a documented vulnerability. 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 ...
How severe is CVE-2026-18674?
CVSS scoring is not yet available for CVE-2026-18674. Check NVD for updates.
Is there a patch for CVE-2026-18674?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.