kuma-dp connects to control plane without verifying TLS certificate when no CA is configured
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
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
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| kumahq | kuma | 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 | 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7 | Patch available | CNA |
| — | github.com/kumahq/kuma/v2 (Go) | before 2.7.26 | 2.7.26 | Patch available | GHSA-wvmp-6r4v-j6cv |
| — | github.com/kumahq/kuma/v2 (Go) | 2.8.0 to before 2.9.16 | 2.9.16 | Patch available | GHSA-wvmp-6r4v-j6cv |
| — | github.com/kumahq/kuma/v2 (Go) | 2.10.0 to before 2.11.14 | 2.11.14 | Patch available | GHSA-wvmp-6r4v-j6cv |
| — | github.com/kumahq/kuma/v2 (Go) | 2.12.0 to before 2.12.11 | 2.12.11 | Patch available | GHSA-wvmp-6r4v-j6cv |
| — | github.com/kumahq/kuma/v2 (Go) | 2.13.0 to before 2.13.7 | 2.13.7 | Patch available | GHSA-wvmp-6r4v-j6cv |
| — | github.com/kumahq/kuma (Go) | up to 1.8.1 | — | No fix listed | GHSA-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
Timeline
- 2026-10-02 Threatist record created from CVE-2026-52724
- 2026-10-03 Alias added: GHSA-wvmp-6r4v-j6cv
- 2026-11-06 Affected versions changed · Red Hat
- 2026-11-06 CVSS score added · Red Hat
References
Other 10
- https://github.com/kumahq/kuma/security/advisories/GHSA-wvmp-6r4v-j6cv
- https://github.com/kumahq/kuma/pull/16777
- https://github.com/kumahq/kuma/commit/2d0fb382924598f8746bc85c896f50384675940f
- https://github.com/kumahq/kuma/commit/85716397ffa404234bf365da0967eca0b0fa1870
- https://github.com/kumahq/kuma/commit/a256af4869ae7e0ebbc2a14dc231e04ac8df1ba3
- https://github.com/kumahq/kuma/commit/bb56ae628753aaec1f7846a514ab4edc35c0b569
- https://github.com/kumahq/kuma/commit/d4ae0c0151596be991897651f20c5cdf32de1980
- https://github.com/kumahq/kuma/commit/eb81494c2c7a5536e55c19cdde51b02a03b51e11
- https://github.com/kumahq/kuma/commit/2ecadac1aa2fd8cded4c2ab768949f4c2ec83e2a
- https://github.com/kumahq/kuma
More kumahq vulnerabilities
- 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
- CVE-2026-52724 · CVE Program
- CVE-2026-52724 · NVD
- FIRST EPSS
- GHSA-wvmp-6r4v-j6cv · GitHub Advisory Database · CC BY 4.0
- CVE-2026-52724 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences