CVE-2026-18677: Kong Mesh: a dataplane token without a workload binding can claim any workload's SPIFFE identity
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kong Meshto a version that resolves this vulnerability.Fixed in 2.13.10 - Upgrade
Upgrade
Kong Meshto a version that resolves this vulnerability.Fixed in 2.14.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-18677?
The severity of CVE-2026-18677 is rated at 75, which indicates a high risk associated with the vulnerability.
What systems are affected by CVE-2026-18677?
CVE-2026-18677 affects Kong Mesh running in universal mode when using a specific MeshIdentity configuration.
How do I fix CVE-2026-18677?
To mitigate CVE-2026-18677, ensure that dataplane tokens are properly bound to workloads, preventing unauthorized access to SPIFFE identities.
What does CVE-2026-18677 exploit?
CVE-2026-18677 exploits the ability of a dataplane token without a workload binding to claim any workload's SPIFFE identity.
Can workload binding be enforced to address CVE-2026-18677?
Yes, enforcing workload binding can effectively address the vulnerability outlined in CVE-2026-18677.