CVE-2026-118759: Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs
The Kubeflow Pipelines API server’s GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler retrieves logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and a suitable pod or node identifier can read live or archived logs using the API server’s permissions.
For live logs, the vulnerable handler also accepts the supplied node ID as a pod name in the run’s namespace without verifying that the pod belongs to the run. Depending on the API server’s pod-log permissions, a known run ID can therefore permit reading the main container logs of an unrelated pod in that namespace. Logs may contain sensitive workload data or credentials.
The affected handler does not authenticate the request itself. An external authentication gate or network policy can restrict reachability; public ingress exposure and unauthenticated enumeration of run IDs are not assumed.
References
- github.com/advisories/GHSA-wg5q-x4j9-qm54
- github.com/kubeflow/pipelines/commit/be4723e33727c6dad71a95cba61e8f61562ab20f
- github.com/kubeflow/pipelines/pull/13684
- github.com/kubeflow/pipelines/releases/tag/2.18.0
- github.com/kubeflow/pipelines/security/advisories/GHSA-wg5q-x4j9-qm54
- nvd.nist.gov/vuln/detail/CVE-2026-118759
Code Behaviors & Features
Detect and mitigate CVE-2026-118759 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →