Most recent entries from all

EUVD-2026-369659

2026-10-09T05:03:44.168674+00:00

EUVD-2026-369659

fkie_cve-2026-50166

2026-10-09T05:03:44.168705+00:00

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.

GHSA-v95x-xhq5-4929 — kumactl connects to control plane without verifying TLS certificate when no CA is configured

2026-10-09T05:03:44.168737+00:00

Affected: Go: github.com/kumahq/kuma/v2, Go: github.com/kumahq/kuma

When an operator adds an HTTPS control plane profile to `kumactl` without providing a CA certificate, `kumactl` disables TLS verification and sends API tokens over the unverified connection

## Impact

An attacker on the network path between the operator and the control plane can intercept user or admin API tokens and then act against the control plane as that user

## Affected configurations

- `kumactl` profiles manually added against an HTTPS control plane endpoint without `--ca-cert-file`

## Not affected

- The default local profile, which uses plain HTTP

## Workarounds

When adding an HTTPS control plane profile to `kumactl`, always pass `--ca-cert-file` pointing at the control plane's serving CA. Alternatively, terminate the control plane behind a publicly trusted certificate; the patched releases will verify successfully against the operating system trust store with no further configuration

## Resources

- Fix: https://github.com/kumahq/kuma/pull/16777