CVE-2026-77596: Kubeflow Pipelines API server lacks authorization for shared pipeline uploads
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the multi-user HTTP endpoints POST /apis/v2beta1/pipelines/upload and POST /apis/v2beta1/pipelines/uploadversion call canUploadVersionedPipeline, which returns without SubjectAccessReview when the target namespace is empty while REQUIRENAMESPACEFORPIPELINES defaults to false. A low-privilege tenant can create shared pipelines or inject attacker-controlled versions into existing shared pipelines without the required write permission; if the API server is directly reachable without an authenticating proxy, an unauthenticated caller can exploit the same bypass, while deployments protected by such a proxy do not expose anonymous access. An enabled unpinned recurring run that follows the latest version can then execute the injected specification in another tenant's namespace under that workload's service account, while pinned or embedded-specification runs are not automatically substituted. This issue is fixed in version 2.18.0.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kubeflow Pipelinesto a version that resolves this vulnerability.Fixed in 2.18.0 - Compensating control
Protect the Kubeflow Pipelines API server with an authenticating proxy so it is not directly reachable by unauthenticated callers.
- Compensating control
Configure recurring runs to use a pinned pipeline version or an embedded pipeline specification rather than automatically following the latest version.