Summary
kumactl connects to control plane without verifying TLS certificate when no CA is configured
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
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
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 versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
github.com/kumahq/kuma/v2 to 2.7.26 or later; github.com/kumahq/kuma/v2 to 2.9.16 or later; github.com/kumahq/kuma/v2 to 2.11.14 or later; github.com/kumahq/kuma/v2 to 2.12.11 or later; github.com/kumahq/kuma/v2 to 2.13.7 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-50166? CVE-2026-50166 is a medium-severity security vulnerability in github.com/kumahq/kuma/v2 (go), affecting versions < 2.7.26. It is fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7.
- Which packages are affected by CVE-2026-50166?
github.com/kumahq/kuma/v2(go) (versions < 2.7.26)github.com/kumahq/kuma(go) (versions <= 1.8.1)
- Is there a fix for CVE-2026-50166? Yes. CVE-2026-50166 is fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7. Upgrade to this version or later.
- Is CVE-2026-50166 exploitable, and should I be worried? Whether CVE-2026-50166 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-50166 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-50166?
- Upgrade
github.com/kumahq/kuma/v2to 2.7.26 or later - Upgrade
github.com/kumahq/kuma/v2to 2.9.16 or later - Upgrade
github.com/kumahq/kuma/v2to 2.11.14 or later - Upgrade
github.com/kumahq/kuma/v2to 2.12.11 or later - Upgrade
github.com/kumahq/kuma/v2to 2.13.7 or later
- Upgrade