CVE-2026-52724 kuma-dp connects to control plane without verifying TLS certificate when no CA is configured
Attackers can intercept dataplane tokens and inject malicious configurations in Kuma Universal mode when TLS verification is disabled by missing CA settings.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-52724?
CVE-2026-52724 is a medium-severity vulnerability in kumahq kuma, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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, Universal mode kuma-dp connections to an HTTPS control plane disable TLS peer verification when --ca-cert-file is not supplied and KUMA_CONTROL_PLANE_CA_CERT is unset. The dataplane authentication token is sent over the unverified connection, allowing an on-path attacker to intercept the token, impersonate the control plane, inject a forged bootstrap configuration, and take over the proxy. Standard Kubernetes installations created by kumactl install control-plane or the official Helm chart are unaffected because the mutating admission webhook injects KUMA_CONTROL_PLANE_CA_CERT into each sidecar. This issue is fixed in versions 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7.
Weakness: CWE-295
Which versions are affected by CVE-2026-52724?
How do I fix CVE-2026-52724?
Upgrade to a fixed version.
Is CVE-2026-52724 being exploited?
There is no known exploitation of CVE-2026-52724 in the wild and no public exploit code.