PoC Monitor
← All CVEs
CVE-2026-18674published 17 Aug 2026 12:08 UTCData: JSON · API

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.0high · scored by CNA · CWE-345
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Kong Inc. Kong Mesh
  • < 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

5 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published17 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.