CVE-2026-88983 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kubeflow Pipelines before 2.17.0 fetches a caller-supplied pipeline URL from the API server without restricting the destination. An authenticated user who can create pipelines can make the server request internal services and learn HTTP status codes, but not response bodies or credentials.
first public Sep 14, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Kubeflow Pipelines before 2.17.0 where users can create pipelines or pipeline versions. The API server's outbound fetch of the pipeline URL is what reaches internal services, so exposure depends on who holds create permission. Teams on 2.17.0 or later are not affected.
Not affected if no-pipeline-create-permission, version-2.17.0-or-later
Who cares kubeflow, kubernetes, ml-platform
2.17.02.17.0Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.17.0, the API server's pipeline and pipeline-version creation paths fetch a caller-supplied pipelineURL without restricting the destination. An authenticated caller with permission to create a pipeline or pipeline version can make requests from the API server to internal services and observe a limited status-code oracle. Arbitrary response-body disclosure, credential theft, and integrity or availability impact are not established. This issue is fixed in version 2.17.0.
This page as ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.