How severe is GHSA-wvmp-6r4v-j6cv?

No CVSS score has been assigned to GHSA-wvmp-6r4v-j6cv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wvmp-6r4v-j6cv?

GHSA-wvmp-6r4v-j6cv affects the following packages: github.com/kumahq/kuma/v2 (Go), github.com/kumahq/kuma/v2 (Go), github.com/kumahq/kuma/v2 (Go), github.com/kumahq/kuma/v2 (Go), github.com/kumahq/kuma/v2 (Go), github.com/kumahq/kuma (Go). Ecosystems affected: Go.

How do I fix GHSA-wvmp-6r4v-j6cv?

Update github.com/kumahq/kuma/v2 to 2.7.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wvmp-6r4v-j6cv is resolved across your whole dependency graph.

How do I detect GHSA-wvmp-6r4v-j6cv in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kumahq/kuma/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-wvmp-6r4v-j6cv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-wvmp-6r4v-j6cv actively exploited in the wild?

No public exploit code has been indexed for GHSA-wvmp-6r4v-j6cv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-wvmp-6r4v-j6cv?

GHSA-wvmp-6r4v-j6cv has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 5th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wvmp-6r4v-j6cv?

GHSA-wvmp-6r4v-j6cv is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wvmp-6r4v-j6cv published, and has it been updated?

GHSA-wvmp-6r4v-j6cv was published on July 16, 2026 and was last updated on August 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

kuma-dp connects to control plane without verifying TLS certificate when no CA is configuredGHSA-wvmp-6r4v-j6cv

Fix: kumahq/kuma#16777

GHSA-wvmp-6r4v-j6cv is a CWE-295 vulnerability in github.com/kumahq/kuma/v2. A fix is available for github.com/kumahq/kuma/v2 — see the affected versions and patch details below.

Also known asCVE-2026-18679 CVE-2026-52724GO-2026-6013

Published

Jul 16, 2026

Updated

Aug 13, 2026

Affected

6 pkgs

Patched

5 / 6

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wvmp-6r4v-j6cv.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs5th percentile — riskier than 5% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

6 pkgs affected

🐹github.com/kumahq/kuma/v2🐹github.com/kumahq/kuma/v2🐹github.com/kumahq/kuma/v2🐹github.com/kumahq/kuma/v2🐹github.com/kumahq/kuma/v2🐹github.com/kumahq/kuma

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 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

Fix: https://github.com/kumahq/kuma/pull/16777

Affected Packages

6 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/kumahq/kuma/v2`	all versions	2.7.26`go get github.com/kumahq/kuma/v2@v2.7.26`
🐹Go	`github.com/kumahq/kuma/v2`	≥ 2.8.0&&< 2.9.16	2.9.16`go get github.com/kumahq/kuma/v2@v2.9.16`
🐹Go	`github.com/kumahq/kuma/v2`	≥ 2.10.0&&< 2.11.14	2.11.14`go get github.com/kumahq/kuma/v2@v2.11.14`
🐹Go	`github.com/kumahq/kuma/v2`	≥ 2.12.0&&< 2.12.11	2.12.11`go get github.com/kumahq/kuma/v2@v2.12.11`
🐹Go	`github.com/kumahq/kuma/v2`	≥ 2.13.0&&< 2.13.7	2.13.7`go get github.com/kumahq/kuma/v2@v2.13.7`
🐹Go	`github.com/kumahq/kuma`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kumahq/kuma/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/kumahq/kuma/v2 to 2.7.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wvmp-6r4v-j6cv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 ## 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 configurations - Universal mode `kuma-dp` started against an HTTPS control plane without `--ca-cert-file` (or `KUMA_CONTROL_PLANE_CA

O3 Security · Impact-Aware SCA

Is GHSA-wvmp-6r4v-j6cv in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works