CVE-2026-50166
Received Received - Intake

Information Disclosure in Kuma Service Mesh

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
CVE-2026-50166
EUVD
EUVD-2026-78773

Affected Vendors & Products

Showing 15 associated CPEs
Vendor Product Version / Range
kuma kuma to 2.7.26 (exc)
kuma kuma to 2.9.16 (exc)
kuma kuma to 2.11.14 (exc)
kuma kuma to 2.12.11 (exc)
kuma kuma to 2.13.7 (exc)
kumahq kuma 2.7.26
kumahq kuma 2.9.16
kumahq kuma 2.11.14
kumahq kuma 2.12.11
kumahq kuma 2.13.7
kumahq kumactl 2.7.26
kumahq kumactl to 2.9.15 (exc)
kumahq kumactl to 2.11.13 (exc)
kumahq kumactl to 2.12.10 (exc)
kumahq kumactl to 2.13.6 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-50166 affects Kuma, a service mesh tool, where manually configured HTTPS control plane profiles without a CA certificate file disable TLS peer verification. This allows API tokens to be sent over unverified connections, which attackers can intercept. The default local profile using plain HTTP is not affected.

Detection Guidance

Check if kumactl profiles are configured for HTTPS control planes without --ca-cert-file. Inspect logs for warnings about insecure TLS verification. Verify if API tokens are transmitted over unverified connections by monitoring network traffic between kumactl and the control plane.

Impact Analysis

An attacker on the network path can intercept user or administrator API tokens and gain unauthorized access to the control plane. This could lead to data breaches, unauthorized control over services, or further attacks within the system.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. Non-compliance may result in legal penalties, data breach notifications, and reputational damage.

Mitigation Strategies

Upgrade Kuma to versions 2.7.26, 2.9.16, 2.11.14, 2.12.11, or 2.13.7 or later. Ensure all kumactl profiles use --ca-cert-file for HTTPS control planes. Avoid using --skip-verify unless absolutely necessary for testing.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-50166. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart