CVE-2026-18674Kong Mesh multi-zone: the global control plane attributes KDS-synced resources by an unvalidated in-band zone identifier
- 7.0HighCVSS base score
- 0.56%Exploitation in 30 daysEPSS · top 53% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Kong
- 14 days later
· 14 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| KongCNA (assigner) | 4.0 | High7.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:L/SI:L/SA:N |
| NVDNVD · Awaiting Analysis | 4.0 | High7.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
- EPSS (exploitation in 30 days)
- 0.56% · top 53% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.
Affected products
What to do
Solution: 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
References9
- Upstream advisory GHSA-m58j-fjmc-h3g4 (opens in a new tab)vendor-advisory
- kumahq/kuma#17456 (master) (opens in a new tab)patch
- kumahq/kuma#17458 (release-2.14 backport) (opens in a new tab)patch
- kumahq/kuma#17461 (release-2.13 backport) (opens in a new tab)patch
- kumahq/kuma#17463 (release-2.12 backport) (opens in a new tab)patch
- kumahq/kuma#17462 (release-2.11 backport) (opens in a new tab)patch
- kumahq/kuma#17460 (release-2.9 backport) (opens in a new tab)patch
- kumahq/kuma#17459 (release-2.7 backport) (opens in a new tab)patch
- Kong Mesh Changelog (opens in a new tab)release-notes
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-60160 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-18674)Record last updated .