The vulnerability in Kubeflow Pipelines allows a caller who can reach the API server and knows a victim run ID and node identifier to retrieve logs from that run without any authorization checks. The GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler does not verify that the node belongs to the requested run, so an attacker can read live or archived logs from a pod in an unrelated namespace. These logs may contain private data or credentials, resulting in a confidentiality breach.

Kubeflow Pipelines prior to version 2.18.0 is affected. Users running any earlier version of the Kubeflow Pipelines component should review the release notes and upgrade to 2.18.0 or later to remediate the issue.

The CVSS score of 7.5 indicates medium to high severity. No EPSS score is available, so the current exploitation probability is unknown. The vulnerability is not listed in the KEV catalog, suggesting no widespread known exploits. The likely attack vector requires network reachability to the API server or an authenticated session, which an attacker can obtain through an externally exposed backend or insufficient network segmentation. Once accessed, the attacker can read logs across tenant boundaries without additional permissions.