CVE-2026-14434 · Infrastructure
NO FIX YET
The kubeturbo agent in IBM Turbonomic versions 8.16.0 through 8.21.2 does not properly validate TLS certificates. A machine-in-the-middle attacker on the network path can obtain sensitive information from the agent's connections.
first public Nov 8, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running IBM Turbonomic with the kubeturbo agent in versions 8.16.0 through 8.21.2 are exposed. An attacker must sit on the network path between the agent and the server it talks to. The sources do not say which connections are affected, so teams on other versions can skip it.
Not affected if version-outside-8.16.0-to-8.21.2
Who cares ibm-turbonomic, kubernetes, kubeturbo
kubectl get deployment kubeturbo -n turbonomic -o jsonpath='{.spec.template.spec.containers[0].image}' (namespace and deployment name may differ)No fix yet, per the sources.
IBM Turbonomic kubeturbo agent 8.16.0 through 8.21.2 does not validate or improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle techniques.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.