medium

CVE-2026-50166

Go · github.com/kumahq/kuma/v2

Summary

kumactl connects to control plane without verifying TLS certificate when no CA is configured

Severity
medium
EPSS
0.3% (p20)
CWE
CWE-295
Also known as
GHSA-v95x-xhq5-4929#github.com/kumahq/kuma/v2
Published
2026-07-16
Updated
2026-07-16

Advisory details

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

Not affected

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

References

Related advisories

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPTClaudePerplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.