CVE-2026-50166mediumCWE-295

CVE-2026-50166: fallo de gravedad media en kumahq kuma

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

Publicada el · Actualizada el

Seguir esta CVE+ Monitorear kuma+ Monitorear github.com/kumahq/kuma

Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.

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.3%
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
CVEs relacionadas — kumahq kuma

En el mismo producto, de las más peligrosas a las menos.

CVE-2026-52724MEDIUMkuma-dp connects to control plane without verifying TLS certificate when no CA is configuredEPSS 0.4%CVE-2026-45021MEDIUMKuma: Default kuma-cp leaks admin token cross-origin via CORS wildcard + LocalhostIsAdminEPSS 0.3%