GPU VulnDB

Database/AI/ML frameworks & serving

Kubeflow Pipelines: unvalidated S3/MinIO endpoint in the UI proxy allows unauthenticated SSRF

CVSS 8.6CVE-2026-88981AI/ML frameworks & servingcurated

Impact

The ml-pipeline-ui frontend accepts an attacker-supplied object-store endpoint (providerInfo.Params.endpoint for source=s3/minio, and S3-compatible endpoint metadata from workflow status for archived pod logs) without requiring it to match the operator-configured storage. In the shipped authorization-disabled standalone configuration an unauthenticated caller can make the shared UI pod fetch arbitrary reachable hosts and return the response body, turning the pipelines UI into an SSRF pivot into the cluster network - node metadata services, in-cluster APIs, and other tenants' services that are not exposed externally. Requests signed with the configured object-store credentials can also disclose an access-key identifier. On an ML cluster this pod typically sits in the same namespace as pipeline storage credentials and is reachable by every data scientist, so it is a cheap foothold for lateral movement. Multi-user secret-backed metadata stays restricted to the server namespace, which limits the credential exposure.

Who can reach it

Anyone who can reach the ml-pipeline-ui service. In the standalone (authorization-disabled) deployment no authentication is needed; in multi-user deployments an authenticated cluster user.

What to do

Upgrade Kubeflow Pipelines to 2.18.0 and roll the ml-pipeline-ui deployment - a standard Kubernetes rollout, no node drain or GPU workload interruption. Until then, do not run the authorization-disabled standalone configuration on a shared or reachable network, and restrict network egress from the UI pod with a NetworkPolicy.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.