CVE-2026-18677: Kong Mesh: a dataplane token without a workload binding can claim any workload's SPIFFE identity
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 48% of scored CVEs
DescriptionCVE.org
In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane's kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with kuma.io/workload set to any value and obtain another workload's SPIFFE identity.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Kong Inc. · Kong Meshfrom 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-18677 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.