Skip to content
Fencer Vulns
medium 5.8

CVE-2026-18679 json

Kong Mesh: kuma-dp connects to the control plane without verifying the TLS certificate when no CA is configured

published 2026-07-16 3 mo ago modified 2026-10-23 16 d ago also CVE-2026-52724 , GHSA-wvmp-6r4v-j6cv , GO-2026-6013 , EUVD-2026-57427

cvss
5.8
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

When kuma-dp is started against an HTTPS control plane and the operator did not pass a CA certificate, the data plane connects with TLS peer verification disabled, and the dataplane authentication token is sent over that unverified connection.

An on-path actor can intercept the dataplane authentication token and impersonate the control plane to the data plane, injecting a forged bootstrap configuration and taking over the proxy.

Patch / fix

  • go github.com/kumahq/kuma/v2 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7
  • Kong Inc. Kong Mesh 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 5.8 CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
CNA 4.0 5.8 CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/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 packages

ecosystem package affected fixed in
go github.com/kumahq/kuma/v2
<2.7.26
>=2.8.0, <2.9.16
>=2.10.0, <2.11.14
>=2.12.0, <2.12.11
>=2.13.0, <2.13.7
>=2.9.13, <2.11.14
>=2.12.4, <2.12.11
2.7.26
2.9.16
2.11.14
2.12.11
2.13.7
go github.com/kumahq/kuma
<=1.8.1
all versions
no fix listed

Affected products

  • Kong Inc. Kong Mesh

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

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.