CVE-2026-18678Kong Mesh: kumactl connects to the control plane without verifying the TLS certificate when no CA is configured
Updated under an hour ago ()
Does this affect you?
It affects Kong Inc. Kong Mesh. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
When an operator adds an HTTPS control plane profile to kumactl without providing a CA certificate, kumactl disables TLS verification and sends API tokens over the unverified connection. An attacker on the network path between the operator and the control plane can intercept user or admin API tokens and then act against the control plane as that user.
- CVSS
- 5.5 MEDIUM (v4.0, CNA)CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
- Weakness (CWE)
- CWE-295
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Kong
- NVD analysis
- Awaiting Analysis
- Record last updated
- Aug 13, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Kong Inc. Kong Mesh kong:mesh (from the name) | before 2.7.26; from 2.8.0 before 2.9.16; from 2.10.0 before 2.11.14; from 2.12.0 before 2.12.11; from 2.13.0 before 2.13.7 | CNA record |
References
- https://github.com/kumahq/kuma/security/advisories/GHSA-v95x-xhq5-4929vendor-advisory
- https://github.com/kumahq/kuma/pull/16777patch
- https://developer.konghq.com/mesh/changelog/release-notes
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.