Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured
Kuma is a modern Envoy-based service mesh that can run on every cloud across both Kubernetes and VMs. Prior to 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7, a kumactl profile manually configured for an HTTPS control plane without --ca-cert-file disables TLS peer verification and sends API tokens over the unverified connection. An attacker on the network path can intercept user or administrator API tokens and act against the control plane as the compromised user. The default local profile is unaffected because it uses plain HTTP. This issue is fixed in versions 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-18678US | — | — | ||
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 conne… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50166.jsonADVISORY
- https://github.com/kumahq/kuma/commit/2d0fb382924598f8746bc85c896f50384675940fFIX
- https://github.com/kumahq/kuma/commit/85716397ffa404234bf365da0967eca0b0fa1870FIX
- https://github.com/kumahq/kuma/commit/a256af4869ae7e0ebbc2a14dc231e04ac8df1ba3FIX
- https://github.com/kumahq/kuma/commit/bb56ae628753aaec1f7846a514ab4edc35c0b569FIX
- https://github.com/kumahq/kuma/commit/d4ae0c0151596be991897651f20c5cdf32de1980FIX
- https://github.com/kumahq/kuma/commit/eb81494c2c7a5536e55c19cdde51b02a03b51e11FIX
- https://github.com/kumahq/kuma/pull/16777FIX
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan