cve.bz

CVE-2026-50166 kumahq kuma: Improper Certificate Validation

5.5 mediumEPSS 0.3%Fix available

Medium (5.5) in kumahq kuma. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/kumahq/kuma/v2 2.11.14, 2.12.11, 2.13.7.

On this page
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.

Severity

CVSS 4.0

5.5 medium
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
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-50166 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50166?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50166?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50166 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
kumahq kuma< 2.7.26

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v95x-xhq5-4929Gogithub.com/kumahq/kuma/v2<2.7.262.7.26
GHSA-v95x-xhq5-4929Gogithub.com/kumahq/kuma/v2>=2.8.0 <2.9.162.9.16
GHSA-v95x-xhq5-4929Gogithub.com/kumahq/kuma/v2>=2.10.0 <2.11.142.11.14
GHSA-v95x-xhq5-4929Gogithub.com/kumahq/kuma/v2>=2.12.0 <2.12.112.12.11
GHSA-v95x-xhq5-4929Gogithub.com/kumahq/kuma/v2>=2.13.0 <2.13.72.13.7
GHSA-v95x-xhq5-4929Gogithub.com/kumahq/kuma<=1.8.1no fix published
GO-2026-6010Gogithub.com/kumahq/kumaall versionsno fix published
GO-2026-6010Gogithub.com/kumahq/kuma/v2<2.7.26
>=2.9.13 <2.11.14
>=2.12.4 <2.12.11
>=2.13.0 <2.13.7
2.7.26, 2.11.14, 2.12.11, 2.13.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON