CVE-2026-18674
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
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
CWEs
CWE-345 CWE-863
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.