Read the docs
TI-2026-37844 Aliases CVE-2026-52724GHSA-wvmp-6r4v-j6cv

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

Priority LOW 26CWE-295Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
Spoofing
Confidentiality · integrity · availability
None · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-295.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0035 28th percentileScored 2026-11-07
Fix Fixed kuma (kumahq): 2.7.26, 2.9.16, 2.11.14 +2github.com/kumahq/kuma/v2 (Go): 2.7.26, 2.9.16, 2.11.14 +2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
kumahqkumabefore 2.7.26; 2.8.0 to before 2.9.16; 2.10.0 to before 2.11.14; 2.12.0 to before 2.12.11; 2.13.0 to before 2.13.72.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7Patch availableCNA
—github.com/kumahq/kuma/v2 (Go)before 2.7.262.7.26Patch availableGHSA-wvmp-6r4v-j6cv
—github.com/kumahq/kuma/v2 (Go)2.8.0 to before 2.9.162.9.16Patch availableGHSA-wvmp-6r4v-j6cv
—github.com/kumahq/kuma/v2 (Go)2.10.0 to before 2.11.142.11.14Patch availableGHSA-wvmp-6r4v-j6cv
—github.com/kumahq/kuma/v2 (Go)2.12.0 to before 2.12.112.12.11Patch availableGHSA-wvmp-6r4v-j6cv
—github.com/kumahq/kuma/v2 (Go)2.13.0 to before 2.13.72.13.7Patch availableGHSA-wvmp-6r4v-j6cv
—github.com/kumahq/kuma (Go)up to 1.8.1—No fix listedGHSA-wvmp-6r4v-j6cv
  • kuma Vendorkumahq Affected before 2.7.26; 2.8.0 to before 2.9.16; 2.10.0 to before 2.11.14; 2.12.0 to before 2.12.11; 2.13.0 to before 2.13.7 Fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7 Patch available CNA
  • github.com/kumahq/kuma/v2 (Go) Vendor— Affected before 2.7.26 Fixed in 2.7.26 Patch available GHSA-wvmp-6r4v-j6cv
  • github.com/kumahq/kuma/v2 (Go) Vendor— Affected 2.8.0 to before 2.9.16 Fixed in 2.9.16 Patch available GHSA-wvmp-6r4v-j6cv
  • github.com/kumahq/kuma/v2 (Go) Vendor— Affected 2.10.0 to before 2.11.14 Fixed in 2.11.14 Patch available GHSA-wvmp-6r4v-j6cv
  • github.com/kumahq/kuma/v2 (Go) Vendor— Affected 2.12.0 to before 2.12.11 Fixed in 2.12.11 Patch available GHSA-wvmp-6r4v-j6cv
  • github.com/kumahq/kuma/v2 (Go) Vendor— Affected 2.13.0 to before 2.13.7 Fixed in 2.13.7 Patch available GHSA-wvmp-6r4v-j6cv
  • github.com/kumahq/kuma (Go) Vendor— Affected up to 1.8.1 Fixed in — No fix listed GHSA-wvmp-6r4v-j6cv

Remediation

  • Fix · CNA kuma (kumahq) Fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7
  • Fix · GHSA-wvmp-6r4v-j6cv github.com/kumahq/kuma/v2 (Go) Fixed in 2.7.26 Advisory →
  • Fix · GHSA-wvmp-6r4v-j6cv github.com/kumahq/kuma/v2 (Go) Fixed in 2.9.16 Advisory →
  • Fix · GHSA-wvmp-6r4v-j6cv github.com/kumahq/kuma/v2 (Go) Fixed in 2.11.14 Advisory →
  • Fix · GHSA-wvmp-6r4v-j6cv github.com/kumahq/kuma/v2 (Go) Fixed in 2.12.11 Advisory →
  • Fix · GHSA-wvmp-6r4v-j6cv github.com/kumahq/kuma/v2 (Go) Fixed in 2.13.7 Advisory →

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-52724
  2. 2026-10-03 Alias added: GHSA-wvmp-6r4v-j6cv
  3. 2026-11-06 Affected versions changed · Red Hat
  4. 2026-11-06 CVSS score added · Red Hat

References

  • TI-2026-32876 Kuma: Default kuma-cp leaks admin token cross-origin via CORS wildcard + LocalhostIsAdmin CVSS 4.0MEDIUM 5.1
  • TI-2026-36929 Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured CVSS 4.0MEDIUM 5.5

Sources