Skip to main content
VulnerabilityPublished

CVE-2026-18676: Kong Mesh · Origin Validation Error

Affects Kong MeshSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium · fixed in 2.13.5 : update Kong Mesh when convenient.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.13.5, 2.12.10, 2.11.13 +2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/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 10 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Kong Inc.Kong MeshAffected
  • >=2.13.0 <2.13.5
Fixed in
  • 2.13.5
Kong Inc.Kong MeshAffected
  • >=2.12.0 <2.12.10
Fixed in
  • 2.12.10
Kong Inc.Kong MeshAffected
  • >=2.10.0 <2.11.13
Fixed in
  • 2.11.13
Kong Inc.Kong MeshAffected
  • >=2.8.0 <2.9.15
Fixed in
  • 2.9.15
Kong Inc.Kong MeshAffected
  • <2.7.25
Fixed in
  • 2.7.25
GitHubkumahq/kumapkg:github/kumahq/kumaOther threatsAffected
  • 2.8.0 – 2.13.0
4 affected builds
Fixed in–

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

AI-suggested

If you cannot patch yet, operators should restrict access to the control plane from browsers or untrusted networks and review CORS configurations to prevent cross-origin token leakage. Monitoring for unusual access patterns and limiting exposure of the control plane to trusted environments is recommended.

Description

The default kuma-cp configuration in Kong Mesh reveals the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. Due to a CORS misconfiguration a cross-origin fetch() from a malicious page returns the admin JWT and signing material.

References

Community reviews

Loading reviews…