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-18678, CVE-2026-50166, GO-2026-6010
kumactl connects to control plane without verifying TLS certificate when no CA is configured
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-fileNot affected
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
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