Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-f7vj-6669-qvv4
Summary
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.
Impact
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.
Patches
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.
Workarounds
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.
Related reports
This is the canonical advisory for the API-server pipeline URL SSRF family. GHSA-wg4h-pp3x-hxhv is tracked as a duplicate submission. Each submission retains its own reporter attribution; this cross-link does not transfer authorship.
Earlier related submission
@pwny0's GHSA-fxx8-rx8w-p9v7, submitted September 23, 2023, included an earlier report of external interaction through the API-server pipeline-package URL path. That portion is consolidated here; its namespace-based frontend SSRF is tracked separately under GHSA-895m-3hxm-h4mg / CVE-2023-6570.
This acknowledges the earlier pipeline-URL submission without attributing fxx8's frontend response-disclosure or cookie-forwarding evidence to the API-server path. @pwny0 retains reporter credit on fxx8; @gasbugs retains reporter credit for this submission. Neither report's authorship is transferred.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a low impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard