How severe is CVE-2026-50166?

No CVSS score has been assigned to CVE-2026-50166 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-50166?

CVE-2026-50166 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 CVE-2026-50166?

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 CVE-2026-50166 is resolved across your whole dependency graph.

How do I detect CVE-2026-50166 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. 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.

How do I mitigate CVE-2026-50166 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.

How does O3 Security protect against CVE-2026-50166?

O3 pinpoints whether CVE-2026-50166 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-50166 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-50166 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.

When was CVE-2026-50166 published, and has it been updated?

CVE-2026-50166 was published on August 12, 2026 and was last updated on September 2, 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

CVE-2026-50166

Fix: kumahq/kuma#16777

CVE-2026-50166 is a security vulnerability in github.com/kumahq/kuma/v2. O3 Security confirms whether CVE-2026-50166 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Kong Mesh: kumactl connects to the control plane without verifying the TLS certificate when no CA is configured

Also known asGHSA-v95x-xhq5-4929GO-2026-6010

Published

Aug 12, 2026

Updated

Sep 2, 2026

Affected

6 pkgs

Patched

5 / 6

Exploits

None indexed

Exploitation data as of Sep 2, 2026 · OSV.dev, 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

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.

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 Packages

6 total 5 fixed

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 dependency

Detect
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 CVE-2026-50166 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 CVE-2026-50166 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 CVE-2026-50166. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2026-50166 in your dependencies?

O3 detects CVE-2026-50166 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works