GPU VulnDB

Database/Container, Kubernetes & orchestration

Kuma: kumactl HTTPS profile without a CA file skips verification and leaks admin API tokens

CVSS 5.5CVE-2026-50166Container, Kubernetes & orchestrationcurated

Impact

A kumactl profile manually pointed at an HTTPS control plane without --ca-cert-file disables TLS peer verification and sends the user's API token over that unverified connection. An attacker on the network path can capture an operator or administrator token and then drive the control plane as that user - mesh policy, traffic permissions and dataplane configuration for the whole cluster. This is the operator-side counterpart to the kuma-dp issue (CVE-2026-52724) and ships in the same releases, but the affected component and the exposed credential differ: this one hands over a human's API token, not a dataplane token. The default local profile uses plain HTTP and is unaffected.

Who can reach it

An attacker on the network path between an operator's workstation running kumactl and the control plane, with the operator using a manually configured HTTPS profile that lacks a CA file. No authentication required of the attacker; it requires the operator to run a command.

What to do

Upgrade to Kuma 2.7.26, 2.9.16, 2.11.14, 2.12.11 or 2.13.7, and set --ca-cert-file in every kumactl profile that targets an HTTPS control plane. Updating kumactl is a client-side binary swap on operator machines, not a fleet maintenance window, but rotate any admin API tokens that were used over an unverified connection.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.