GHSA-v95x-xhq5-4929
Fix: kumahq/kuma#16777GHSA-v95x-xhq5-4929 is a CWE-295 vulnerability in github.com/kumahq/kuma/v2. O3 Security confirms whether GHSA-v95x-xhq5-4929 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
kumactl connects to control plane without verifying TLS certificate when no CA is configured
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-v95x-xhq5-4929.
Real-World Exposure
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/kumaReal-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
When an operator adds an HTTPS control plane profile to kumactl without providing a CA certificate, kumactl disables TLS verification and sends API tokens over the unverified connection
Impact
An attacker on the network path between the operator and the control plane can intercept user or admin API tokens and then act against the control plane as that user
Affected configurations
kumactlprofiles manually added against an HTTPS control plane endpoint without--ca-cert-file
Not affected
- The default local profile, which uses plain HTTP
Workarounds
When adding an HTTPS control plane profile to kumactl, always pass --ca-cert-file pointing 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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/kumahq/kuma/v2 | all versions | 2.7.26 |
| 🐹Go | github.com/kumahq/kuma/v2 | ≥ 2.8.0&&< 2.9.16 | 2.9.16 |
| 🐹Go | github.com/kumahq/kuma/v2 | ≥ 2.10.0&&< 2.11.14 | 2.11.14 |
| 🐹Go | github.com/kumahq/kuma/v2 | ≥ 2.12.0&&< 2.12.11 | 2.12.11 |
| 🐹Go | github.com/kumahq/kuma/v2 | ≥ 2.13.0&&< 2.13.7 | 2.13.7 |
| 🐹Go | github.com/kumahq/kuma | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kumahq/kuma/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-v95x-xhq5-4929 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.
How O3 protects you
O3 pinpoints whether GHSA-v95x-xhq5-4929 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-v95x-xhq5-4929. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v95x-xhq5-4929 in your dependencies?
O3 detects GHSA-v95x-xhq5-4929 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.