The Kubeflow Pipelines API server fetched caller-supplied pipeline package URLs without restricting the destination. A caller authorized to create a pipeline or pipeline version could cause requests to originate from the API server's network position, including to internal services that the caller could not otherwise reach.
The reported evidence demonstrates blind server-side request forgery and a limited status-code oracle. The fetched response is processed as a pipeline package; the report does not demonstrate arbitrary response-body disclosure or credential theft. A request to a cloud metadata endpoint returned HTTP 403, which does not establish access to metadata contents or tokens.
The confidentiality metric is Low to reflect the limited information obtainable through the status-code oracle. High confidentiality impact and integrity or availability impact are not established by the submitted evidence. Impact depends on the API server's network reachability and the deployment's trust boundaries.
Fixed by kubeflow/pipelines#12750, first released in 2.17.0. The fix validates URL schemes, ports, allowed domains, and resolved IP addresses; validates redirects; and enforces IP restrictions at connection time. The HTTP client also applies timeouts and disables environment proxy use so connections pass through the validated dialer.
Operators should keep pipeline URL validation enabled and limit additional allowed domains to trusted pipeline sources.
Until upgrading, restrict API-server egress to required destinations through deployment-specific network controls. Account for required Kubernetes and storage connectivity when applying these restrictions.
This is the canonical advisory for the API-server pipeline URL SSRF family. GHSA-wg4h-pp3x-hxhv is tracked as a...
0.0.0-20260517162502-504d7797c1e0Exploitability
AV:NAC:LPR:LUI:NScope
S:CImpact
C:LI:NA:N5.0/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NInput Validation
Other