CVE-2026-50166mediumCWE-295

CVE-2026-50166: falha de média gravidade em kumahq kuma

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

Publicada em · Atualizada em

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

Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.

13Vexday Risk Score

Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.

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
Produtos afetados
kumahq · kuma
CVEs relacionadas — kumahq kuma

No mesmo produto, das mais perigosas para as 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%