Live › vulnerability › CVE-2026-118759
The Kubeflow Pipelines API server's run log endpoint did not check whether the caller was allowed to read the selected run, so a caller who reaches the backend and knows a run ID and node ID can read that run's logs, or logs of an unrelated pod, using the API server's permissions. Logs can contain sensitive workload data or credentials.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 17:26 UTC. All times on this page are UTC.
Teams running Kubeflow Pipelines before 2.18.0 where the API server can be reached by callers who are not already trusted. The flaw lets a reachable caller read run logs, and for live logs read unrelated pods in a namespace, once they know a run ID and a node or pod identifier. Installations where an external authentication gate or network policy blocks access to the API server are less exposed, but the handler itself does no authentication.
No product ranges from the sources yet.
kubectl get deploy -A and inspecting the image tag of the ml-pipeline API server2.18.02.18.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the API server's GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler retrieved logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and suitable pod or node identifier can read live or archived logs with the API server's permissions. For live logs, the caller-controlled node ID was also accepted as a pod name without verifying that the pod belonged to the requested run, allowing a known run ID to select the namespace of an unrelated pod and read its main container logs. The handler does not authenticate requests itself, although an external authentication gate or network policy can limit reachability. Exposed logs can contain sensitive workload data or credentials. This issue is fixed in version 2.18.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-118759")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.