CVE-2026-52724

CVE-2026-52724 is a medium-severity security vulnerability in github.com/kumahq/kuma/v2 (go), affecting versions < 2.7.26. It is fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

When kuma-dp is started against an HTTPS control plane and the operator did not pass a CA certificate, the data plane connects with TLS peer verification disabled. The dataplane authentication token is sent over this unverified connection

Affected configurations

  • Universal mode kuma-dp started against an HTTPS control plane without --ca-cert-file (or KUMA_CONTROL_PLANE_CA_CERT unset)

Not affected

  • Kubernetes installs done through the standard installers (kumactl install control-plane or the official Helm chart). In both cases the control plane's mutating admission webhook injects KUMA_CONTROL_PLANE_CA_CERT into every sidecar at pod admission, so each kuma-dp starts with the CA already configured

Workarounds

Set --ca-cert-file (or KUMA_CONTROL_PLANE_CA_CERT) on every Universal mode data plane and point it 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

Impact

An on-path attacker can intercept the dataplane authentication token and impersonate the control plane to the data plane, allowing them to inject a forged bootstrap configuration and take over the proxy

Affected versions

github.com/kumahq/kuma/v2 (< 2.7.26) github.com/kumahq/kuma/v2 (>= 2.8.0, < 2.9.16) github.com/kumahq/kuma/v2 (>= 2.10.0, < 2.11.14) github.com/kumahq/kuma/v2 (>= 2.12.0, < 2.12.11) github.com/kumahq/kuma/v2 (>= 2.13.0, < 2.13.7) github.com/kumahq/kuma (<= 1.8.1)

Security releases

github.com/kumahq/kuma/v2 → 2.7.26 (go) github.com/kumahq/kuma/v2 → 2.9.16 (go) github.com/kumahq/kuma/v2 → 2.11.14 (go) github.com/kumahq/kuma/v2 → 2.12.11 (go) github.com/kumahq/kuma/v2 → 2.13.7 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

github.com/kumahq/kuma/v2 to 2.7.26 or later; github.com/kumahq/kuma/v2 to 2.9.16 or later; github.com/kumahq/kuma/v2 to 2.11.14 or later; github.com/kumahq/kuma/v2 to 2.12.11 or later; github.com/kumahq/kuma/v2 to 2.13.7 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-52724? CVE-2026-52724 is a medium-severity security vulnerability in github.com/kumahq/kuma/v2 (go), affecting versions < 2.7.26. It is fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7.
  2. Which packages are affected by CVE-2026-52724?
    • github.com/kumahq/kuma/v2 (go) (versions < 2.7.26)
    • github.com/kumahq/kuma (go) (versions <= 1.8.1)
  3. Is there a fix for CVE-2026-52724? Yes. CVE-2026-52724 is fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7. Upgrade to this version or later.
  4. Is CVE-2026-52724 exploitable, and should I be worried? Whether CVE-2026-52724 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-52724 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-52724?
    • Upgrade github.com/kumahq/kuma/v2 to 2.7.26 or later
    • Upgrade github.com/kumahq/kuma/v2 to 2.9.16 or later
    • Upgrade github.com/kumahq/kuma/v2 to 2.11.14 or later
    • Upgrade github.com/kumahq/kuma/v2 to 2.12.11 or later
    • Upgrade github.com/kumahq/kuma/v2 to 2.13.7 or later

Other vulnerabilities in github.com/kumahq/kuma/v2

CVE-IDSeverityPackage summary
CVE-2026-50166Mediumgithub.com/kumahq/kuma/v2: kumactl connects to control plane without verifying TLS certificate when no CA is configured

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo