CVE-2026-88983

CVE-2026-88983 is a medium-severity server-side request forgery (SSRF) vulnerability in github.com/kubeflow/pipelines (go), affecting versions < 0.0.0-20260517162502-504d7797c1e0. It is fixed in 0.0.0-20260517162502-504d7797c1e0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Kubeflow Pipelines, API server fetches a caller-supplied pipelineURL without host validation

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.

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.

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.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-88983 has a CVSS score of 5.0 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260517162502-504d7797c1e0); upgrading removes the vulnerable code path.

Affected versions

github.com/kubeflow/pipelines (< 0.0.0-20260517162502-504d7797c1e0)

Security releases

github.com/kubeflow/pipelines → 0.0.0-20260517162502-504d7797c1e0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

  1. What is CVE-2026-88983? CVE-2026-88983 is a medium-severity server-side request forgery (SSRF) vulnerability in github.com/kubeflow/pipelines (go), affecting versions < 0.0.0-20260517162502-504d7797c1e0. It is fixed in 0.0.0-20260517162502-504d7797c1e0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
  2. How severe is CVE-2026-88983? CVE-2026-88983 has a CVSS score of 5.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of github.com/kubeflow/pipelines are affected by CVE-2026-88983? github.com/kubeflow/pipelines (go) versions < 0.0.0-20260517162502-504d7797c1e0 is affected.
  4. Is there a fix for CVE-2026-88983? Yes. CVE-2026-88983 is fixed in 0.0.0-20260517162502-504d7797c1e0. Upgrade to this version or later.
  5. Is CVE-2026-88983 exploitable, and should I be worried? Whether CVE-2026-88983 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-88983 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-88983? Upgrade github.com/kubeflow/pipelines to 0.0.0-20260517162502-504d7797c1e0 or later.

Other vulnerabilities in github.com/kubeflow/pipelines

Stop the waste.
Protect your environment with Kodem.