CVE-2026-50166mediumCWE-295

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

13Vexday Risk Score

Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.

ssvc Trackcvss 5.5epss 0.2%

probabilidad de explotación

0.2%top 92% de las CVE

explotación observada

noninguna fuente lo reporta

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.

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

Productos afectados

kumahq · kuma

Referencias

https://github.com/kumahq/kuma/commit/2d0fb382924598f8746bc85c896f50384675940f https://github.com/kumahq/kuma/commit/85716397ffa404234bf365da0967eca0b0fa1870 https://github.com/kumahq/kuma/commit/a256af4869ae7e0ebbc2a14dc231e04ac8df1ba3 https://github.com/kumahq/kuma/commit/bb56ae628753aaec1f7846a514ab4edc35c0b569 https://github.com/kumahq/kuma/commit/d4ae0c0151596be991897651f20c5cdf32de1980 https://github.com/kumahq/kuma/commit/eb81494c2c7a5536e55c19cdde51b02a03b51e11 https://github.com/kumahq/kuma/pull/16777 https://github.com/kumahq/kuma/security/advisories/GHSA-v95x-xhq5-4929