github.com/kumahq/kuma/v2
Affected
- introduced
0, fixed2.7.26(semver)
Fixed versions
2.7.26
Fix
- Fixed version
2.7.26go get github.com/kumahq/kuma/[email protected]
Advisory
Also known as: CVE-2026-18679, CVE-2026-52724, GO-2026-6013
kuma-dp connects to control plane without verifying TLS certificate when no CA is configured
When kuma-dp is started against an HTTPS control plane and the operator did not pass a CA certificate, the data plane connects with TLS peer verification disabled. The dataplane authentication token is sent over this unverified connection
Impact
An on-path attacker can intercept the dataplane authentication token and impersonate the control plane to the data plane, allowing them to inject a forged bootstrap configuration and take over the proxy
Affected configurations
kuma-dp started against an HTTPS control plane without --ca-cert-file (or KUMA_CONTROL_PLANE_CA_CERT unset)Not affected
kumactl install control-plane or the official Helm chart). In both cases the control plane's mutating admission webhook injects KUMA_CONTROL_PLANE_CA_CERT into every sidecar at pod admission, so each kuma-dp starts with the CA already configuredWorkarounds
Set --ca-cert-file (or KUMA_CONTROL_PLANE_CA_CERT) on every Universal mode data plane and point it 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
Medium Basis: The source's own band: MODERATE
0, fixed 2.7.26 (semver)2.7.26
2.7.26go get github.com/kumahq/kuma/[email protected]2.8.0, fixed 2.9.16 (semver)2.9.16
2.9.16go get github.com/kumahq/kuma/[email protected]2.10.0, fixed 2.11.14 (semver)2.11.14
2.11.14go get github.com/kumahq/kuma/[email protected]2.12.0, fixed 2.12.11 (semver)2.12.11
2.12.11go get github.com/kumahq/kuma/[email protected]2.13.0, fixed 2.13.7 (semver)2.13.7
2.13.7go get github.com/kumahq/kuma/[email protected]0, last affected 1.8.1 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0