CVE-2026-52724 PUBLISHED

kuma-dp connects to control plane without verifying TLS certificate when no CA is configured

Assigner: GitHub_M
Reserved: 08.06.2026 Published: 15.09.2026 Updated: 15.09.2026

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.

Metrics

CVSS Vector: CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
CVSS Score: 5.8

Product Status

Vendor kumahq
Product kuma
Versions
  • Version < 2.7.26 is affected
  • Version >= 2.8.0, < 2.9.16 is affected
  • Version >= 2.10.0, < 2.11.14 is affected
  • Version >= 2.12.0, < 2.12.11 is affected
  • Version >= 2.13.0, < 2.13.7 is affected

References

Problem Types

  • CWE-295: Improper Certificate Validation CWE