Skip to main content
VulnerabilityPublished

CVE-2026-18677: Kong Mesh · Authentication Bypass by Spoofing

Affects Kong MeshSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 2.14.2 or 2.13.10 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.14.2, 2.13.10
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Kong Mesh to 2.14.2 or 2.13.10.

Affected software

ProductAffectedFixed in
Kong Inc.Kong MeshAffected
  • >=2.14.0 <2.14.2
Fixed in
  • 2.14.2
Kong Inc.Kong MeshAffected
  • >=2.13.0 <2.13.10
Fixed in
  • 2.13.10
GitHubkumahq/kumapkg:github/kumahq/kumaOther threatsAffected
  • =2.13.0
  • =2.14.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor Kong Inc.'s advisories for updates and consider restricting token issuance or enforcing workload binding where possible to reduce risk.

Description

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.

References

Community reviews

Loading reviews…