CVSS 4.0
5.8 mediumCVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:HMedium (5.8) in kumahq kuma. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/kumahq/kuma/v2 2.11.14, 2.12.11, 2.13.7.
CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:Hgithub.com/kumahq/kuma/v2 (Go): fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7Explain CVE-2026-52724 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-52724?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-52724?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-52724 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| kumahq kuma | < 2.7.26 |
| kumahq kuma | >= 2.8.0, < 2.9.16 |
| kumahq kuma | >= 2.10.0, < 2.11.14 |
| kumahq kuma | >= 2.12.0, < 2.12.11 |
| kumahq kuma | >= 2.13.0, < 2.13.7 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-wvmp-6r4v-j6cv | Go | github.com/kumahq/kuma/v2 | <2.7.26 | 2.7.26 |
| GHSA-wvmp-6r4v-j6cv | Go | github.com/kumahq/kuma/v2 | >=2.8.0 <2.9.16 | 2.9.16 |
| GHSA-wvmp-6r4v-j6cv | Go | github.com/kumahq/kuma/v2 | >=2.10.0 <2.11.14 | 2.11.14 |
| GHSA-wvmp-6r4v-j6cv | Go | github.com/kumahq/kuma/v2 | >=2.12.0 <2.12.11 | 2.12.11 |
| GHSA-wvmp-6r4v-j6cv | Go | github.com/kumahq/kuma/v2 | >=2.13.0 <2.13.7 | 2.13.7 |
| GHSA-wvmp-6r4v-j6cv | Go | github.com/kumahq/kuma | <=1.8.1 | no fix published |
| GO-2026-6013 | Go | github.com/kumahq/kuma | all versions | no fix published |
| GO-2026-6013 | Go | github.com/kumahq/kuma/v2 | <2.7.26 >=2.9.13 <2.11.14 >=2.12.4 <2.12.11 >=2.13.0 <2.13.7 | 2.7.26, 2.11.14, 2.12.11, 2.13.7 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.
Red Hat rates this Moderate.
This vulnerability is rated as having Moderate impact because exploitation requires an attacker to be positioned on the network path between the data plane and the control plane under a non-default configuration where TLS verification is omitted. Standard Kubernetes and OpenShift environments are unaffected as admission webhooks automatically provision the control plane Certificate Authority (CA) into sidecars. Impact is therefore limited to Universal deployments where `kuma-dp` runs on standalone hosts or virtual machines without an explicitly specified CA certificate.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-52724.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.