CVE-2026-50166

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

State
Published
Severity
5.5 Medium
Published
Sep 15, 2026
Updated
Sep 16, 2026
Reserved
Jun 3, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
4.05.5 MediumCVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:HGitHub_M

Weaknesses

  • CWE-295 Improper Certificate Validation

Affected Products

ProductVersions
kumakumahq
  • < 2.7.26Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.