Answer in brief
CVE-2026-18679 records a Medium severity (CVSS 5.8) vulnerability in kuma-dp connects to control plane without verifying TLS certificate when no CA is configured. The current sources do not mark it as known exploited. The current feed maps Kong Inc./Kong Mesh (generic), kumahq/kuma (generic), github.com/kumahq/kuma (go), github.com/kumahq/kuma (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Kong Inc./Kong Mesh (generic), kumahq/kuma (generic), github.com/kumahq/kuma (go), github.com/kumahq/kuma (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Kong Inc./Kong Meshgeneric | >=0 <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 | 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7 |
| kumahq/kumageneric | <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 | 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7 |
| github.com/kumahq/kumago | <=1.8.1 | Not reported |
| github.com/kumahq/kumago | >=0 | Not reported |
| github.com/kumahq/kuma/v2go | <2.7.26 | 2.7.26 |
| github.com/kumahq/kuma/v2go | >=2.8.0,<2.9.16 | 2.9.16 |
| github.com/kumahq/kuma/v2go | >=2.10.0,<2.11.14 | 2.11.14 |
| github.com/kumahq/kuma/v2go | >=2.12.0,<2.12.11 | 2.12.11 |
| github.com/kumahq/kuma/v2go | >=2.13.0,<2.13.7 | 2.13.7 |
| github.com/kumahq/kuma/v2go | >=0 <2.7.26 | 2.7.26 |
| github.com/kumahq/kuma/v2go | >=2.8.0 <2.9.16 | 2.9.16 |
| github.com/kumahq/kuma/v2go | >=2.10.0 <2.11.14 | 2.11.14 |
| github.com/kumahq/kuma/v2go | >=2.12.0 <2.12.11 | 2.12.11 |
| github.com/kumahq/kuma/v2go | >=2.13.0 <2.13.7 | 2.13.7 |
| github.com/kumahq/kuma/v2go | >=0 <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 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 16, 2026
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, Universal mode kuma-dp connections to an HTTPS control plane disable TLS peer verification when --ca-cert-file is not supplied and KUMA_CONTROL_PLANE_CA_CERT is unset. The dataplane authentication token is sent over the unverified connection, allowing an on-path attacker to intercept the token, impersonate the control plane, inject a forged bootstrap configuration, and take over the proxy. Standard Kubernetes installations created by kumactl install control-plane or the official Helm chart are unaffected because the mutating admission webhook injects KUMA_CONTROL_PLANE_CA_CERT into each sidecar. This issue is fixed in versions 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7.
Quoted source text, attributed separately from HOL analysis.