CVE-2026-52724

MEDIUMPre-NVD 5.85.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.8
EG Score
5.8(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity58% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 16, 2026

Last Modified

September 15, 2026

Advisory Details (8)

Auto-updated Sep 15, 2026
Patch available. Sources: github_pr, github_commit, github.
github_commit Patch Available

commit eb81494c2c7a (kumahq/kuma)

Patch available: kumahq/kuma v2.13.7 (contains commit eb81494c2c7a)

https://github.com/kumahq/kuma/commit/eb81494c2c7a5536e55c19cdde51b02a03b51e11
github_commit

commit d4ae0c015159 (kumahq/kuma)

Fix landed in kumahq/kuma commit d4ae0c015159 — awaiting tagged release

https://github.com/kumahq/kuma/commit/d4ae0c0151596be991897651f20c5cdf32de1980
github_commit Patch Available

commit bb56ae628753 (kumahq/kuma)

Patch available: kumahq/kuma v2.7.27 (contains commit bb56ae628753)

https://github.com/kumahq/kuma/commit/bb56ae628753aaec1f7846a514ab4edc35c0b569
github_commit Patch Available

commit a256af4869ae (kumahq/kuma)

Patch available: kumahq/kuma 2.9.16 (contains commit a256af4869ae)

https://github.com/kumahq/kuma/commit/a256af4869ae7e0ebbc2a14dc231e04ac8df1ba3
github_commit Patch Available

commit 85716397ffa4 (kumahq/kuma)

Patch available: kumahq/kuma v2.12.11 (contains commit 85716397ffa4)

https://github.com/kumahq/kuma/commit/85716397ffa404234bf365da0967eca0b0fa1870
github_commit Patch Available

commit 2d0fb3829245 (kumahq/kuma)

Patch available: kumahq/kuma v2.11.14 (contains commit 2d0fb3829245)

https://github.com/kumahq/kuma/commit/2d0fb382924598f8746bc85c896f50384675940f
github_pr Patch Available

fix(kuma-cp): use system trust when CA cert is not provided

Patch available: kumahq/kuma v2.14.0 (PR #16777 merged 2026-05-29)

https://github.com/kumahq/kuma/pull/16777
github Patch Available

kuma-dp connects to control plane without verifying TLS certificate when no CA is configured · Advisory · kumahq/kuma · GitHub

https://github.com/kumahq/kuma/security/advisories/GHSA-wvmp-6r4v-j6cv

Vendor Advisories for CVE-2026-52724(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/kumahq/kuma———
github.com/kumahq/kuma/v2—2.13.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 09:56 UTCEG score recompute
  3. 2026-09-17 10:29 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-15 16:35 UTCEG score recompute
  6. 2026-09-15 15:35 UTCEG score recompute
  7. 2026-09-15 14:58 UTCEG score recompute▲ 5.80
  8. 2026-09-15 14:57 UTCMITRE cvelistV5CVSS v3 → 5.8 · CVSS v4 → 5.8
  9. 2026-08-01 11:12 UTCEG score recompute
  10. 2026-07-26 11:24 UTCEG score recompute
  11. 2026-07-23 03:19 UTCEG score recompute
  12. 2026-07-16 20:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52724?
CVE-2026-52724 is a medium vulnerability published on July 16, 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…
When was CVE-2026-52724 disclosed?
CVE-2026-52724 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52724 actively exploited?
CVE-2026-52724 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.2% of all scored CVEs.
What is the CVSS score of CVE-2026-52724?
CVE-2026-52724 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-52724?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52724, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52724

Explore →

Is Your Infrastructure Affected by CVE-2026-52724?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs