Kubeflow Pipelines CVE-2026-118759 (run-log endpoint reads pod logs without authorization) and CVE-2026-118761 (pipeline archive upload decompression bomb): which release fixes them?

What it is: Kubeflow Pipelines (KFP) runs ML workflows on Kubernetes. Two high advisories were published on October 30, 2026: - CVE-2026-118759 (GHSA-wg5q-x4j9-qm54): the API server's run-log endpoint (GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log) returned logs without checking that the caller may access that run, and for live logs accepted a pod name without checking it belongs to the run. Someone who can reach the API and knows a run ID could read other users' pipeline logs, and possibly logs of other pods in that namespace. Pipeline logs often contain data paths, parameters and sometimes credentials. - CVE-2026-118761 (GHSA-8fmv-6rg5-5924): uploaded pipeline archives (ZIP or tar.gz) were decompressed without bounding their expanded size, before authorization, so a small archive could exhaust the API server's memory. Both are fixed in Kubeflow Pipelines 2.18.0. Am I affected: - Kubeflow Pipelines releases before 2.18.0 (standalone KFP or as part of a Kubeflow platform deployment). Check the ml-pipeline API server image tag: kubectl get deploy ml-pipeline -n kubeflow -o jsonpath='{.spec.template.spec.containers[0].image}'. - Exposure depends on who can reach the KFP API: multi-user clusters and deployments reachable beyond the platform team are most at risk. Fix: 1. Upgrade Kubeflow Pipelines to 2.18.0 or later (or the Kubeflow platform release that includes it). 2. Until then, restrict network access to the ml-pipeline API service (Istio authorization policies or NetworkPolicies, and authentication in front of it), and limit request body sizes at the ingress for upload endpoints. 3. Keep secrets out of pipeline logs (use Kubernetes secrets and avoid printing them), and rotate any credentials that may have appeared in logs on multi-user clusters. Verify: the API server image shows 2.18.0+, and a request for another user's run logs is refused. Sources: https://github.com/kubeflow/pipelines/security/advisories/GHSA-wg5q-x4j9-qm54 https://github.com/kubeflow/pipelines/security/advisories/GHSA-8fmv-6rg5-5924 https://github.com/kubeflow/pipelines/releases/tag/2.18.0