CVE-2026-50166 PUBLISHED

Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured

Assigner: GitHub_M
Reserved: 03.06.2026 Published: 15.09.2026 Updated: 15.09.2026

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.

Metrics

CVSS Vector: 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
CVSS Score: 5.5

Product Status

Vendor kumahq
Product kuma
Versions
  • Version < 2.7.26 is affected

References

Problem Types

  • CWE-295: Improper Certificate Validation CWE