Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows

Why it is Yellow

• CVSS 6.5 medium

References

• https://github.com/kubeflow/pipelines/commit/fb69119c997402ebddab4f6410c617cb3d3634ba
• https://github.com/kubeflow/pipelines/issues/9889
• https://github.com/kubeflow/pipelines/pull/12860
• https://github.com/kubeflow/pipelines/releases/tag/2.17.0
• https://github.com/kubeflow/pipelines/security/advisories/GHSA-vjhf-6c8f-qhwj

Original description

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. From 0.5.1 until 2.17.0, the frontend artifact routes did not check whether an authenticated user was authorized to access the requested namespace. A user who can reach the frontend and knows an artifact location can select another tenant's namespace, or omit the namespace and reach an unguarded direct handler, to read artifact contents such as datasets, models, or pipeline outputs. The issue applies to multi-user deployments that rely on Kubeflow Pipelines authorization for tenant isolation. Authentication at ingress identifies the caller but does not authorize access to the selected artifact namespace. The issue does not establish arbitrary Kubernetes Secret disclosure, storage modification, or server-side code execution. This issue is fixed in version 2.17.0.