Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5

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

CVE-2026-50166GHSA-v95x-xhq5-4929

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/kumahq/kuma

    Affected
    <= 1.8.1
    Fixed in
    no fixed version recorded

  • Go github.com/kumahq/kuma/v2

    Affected
    < 2.7.26>= 2.8.0, < 2.9.16>= 2.10.0, < 2.11.14>= 2.12.0, < 2.12.11>= 2.13.0, < 2.13.7
    Fixed in
    2.7.26, 2.13.7, 2.11.14, 2.9.16, 2.12.11

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.5 · 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 · score source
EPSS
  • CVE-2026-50166: 0.27% estimated exploitation activity in the next 30 days; percentile 19.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 - kumactl profiles 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 - Fix: https://github.com/kumahq/kuma/pull/16777

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-v95x-xhq5-4929

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-50166

Advisory: kumactl connects to control plane without verifying TLS certificate when no CA is configured
IDs: CVE-2026-50166, GHSA-v95x-xhq5-4929
Record: https://patchnext.com/advisories/cve-2026-50166 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/kumahq/kuma/v2 2.13.7, 2.12.11, 2.11.14, 2.9.16, 2.7.26. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kumahq/kuma: affected <= 1.8.1
- Go github.com/kumahq/kuma/v2: affected < 2.7.26; >= 2.8.0, < 2.9.16; >= 2.10.0, < 2.11.14; >= 2.12.0, < 2.12.11; >= 2.13.0, < 2.13.7; fixed in 2.7.26, 2.13.7, 2.11.14, 2.9.16, 2.12.11

## Suggested inspection (read-only)
- Go github.com/kumahq/kuma: check the installed version with your package manager.
- Go github.com/kumahq/kuma/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kumahq/kuma, github.com/kumahq/kuma/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v95x-xhq5-4929 (GitHub-reviewed advisory GHSA-v95x-xhq5-4929 lists affected ranges: Go github.com/kumahq/kuma/v2 >=0 =2.8.0 =2.10.0 =2.12.0 =2.13.0 =0 <=1.8.1)

Commands are suggestions: review each one before running it.

Loading voting…