Skip to content
OpenAdvisories
Medium · 5.5 CVE-2026-50166 EUVD-2026-78773GHSA-v95x-xhq5-4929

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

Published Sep 15, 2026 · Updated Sep 16, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
kumahq kuma < 2.7.26 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Leap 16.0 govulncheck-vulndb 0.0.20260723T184607-160000.1.1 openSUSE-SU-2026:21483-1

Advisories 1

References