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