CVE-2026-18677 json
Kong Mesh: a dataplane token without a workload binding can claim any workload's SPIFFE identity
published 2026-08-12 2 mo ago modified 2026-10-23 16 d ago also EUVD-2026-57424
- cvss
- 6.0
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Kong Inc. Kong Mesh 2.13.10, 2.14.2
- github.com/kumahq/kuma#17474 pull request
- github.com/kumahq/kuma#17503 pull request
- github.com/kumahq/kuma#17502 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/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 |
Affected products
- Kong Inc. Kong Mesh
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
-
github.com
/kumahq/kuma/pull/17474
patch
-
github.com
/kumahq/kuma/pull/17503
patch
-
github.com
/kumahq/kuma/pull/17502
patch
-
github.com
/kumahq/kuma/security/advisories/GHSA-744g-c785-x65q
vendor-advisory
-
developer.konghq.com
/mesh/changelog/
release-notes
Sources
- CVE List CVE-2026-18677
- NVD CVE-2026-18677
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.