CVE-2026-18674: Kong Mesh multi-zone: the global control plane attributes KDS-synced resources by an unvalidated in-band zone identifier
Kong Inc. · Kong Mesh
Vendor fix available · Affected: Kong Inc. Kong Mesh · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 47% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Kong Inc. · Kong Meshbefore 2.7.29; from 2.8.0 before 2.9.19; from 2.10.0 before 2.11.18; from 2.12.0 before 2.12.14; from 2.13.0 before 2.13.10; from 2.14.0 before 2.14.2
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Kong Inc.
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-18674 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.