CVE-2026-18674
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.
What this means for your business
- FIRST's prediction model gives it a 0.4% chance of attack attempts being seen in the next 30 days, ranking above 31% of all known flaws.
What to do
- 1Ask your IT team or provider whether any of your systems use the affected product.
- 2If you do, follow the vendor's guidance. No patch reference has been published yet.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- Not yet scored
- CVSS v4
- 7.0
- Weakness
- CWE-345
- Assigned by
- 02762ae7-200e-4b20-9b2b-a77d5b8fc4cb
Dates
- Published
- 2026-08-17
- Last modified
- 2026-08-31
- Sources
- NVD
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