Kubeflow Pipelines
Kubeflow Pipelines: Unauthenticated SSRF through artifact provider endpoints
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the frontend artifact download path for source=s3 or source=minio accepts providerInfo.Params.endpoint, and the archived pod-log path accepts S3-compatible endpoint metadata from workflow status, without requiring those endpoints to match operator-controlled storage configuration. In the shipped authorization-disabled standalone configuration, an unauthenticated caller can make the shared ml-pipeline-ui pod connect to arbitrary reachable hosts and return response data; requests may also reveal an access-key identifier when signed with configured object-store credentials. Multi-user secret-backed metadata remains restricted to the server namespace. This issue is fixed in version 2.18.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.18.0
Fixed in 2.18.0
Mitigation
Upgrade pipelines to 2.18.0 or later.
References
- Vendor advisory github.com/kubeflow/pipelines/security/advisor…
- Patch github.com/kubeflow/pipelines/pull/14349
- Patch github.com/kubeflow/pipelines/commit/0b77f9b07…
1 more
- Release notes github.com/kubeflow/pipelines/releases/tag/2.1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.