Quick answers
- Is CVE-2026-88983 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88983 being exploited in the wild.
- How severe is CVE-2026-88983?
- Medium severity, with a CVSS score of 5, published 5 November 2026.
- Which products and versions are affected?
- github.com/kubeflow/pipelines (Go) < 0.0.0-20260517162502-504d7797c1e0, SEMVER:introduced=0,fixed=0.0.0-20260517162502-504d7797c1e0; Kubeflow Pipelines prior to 2.17.0.
- Is there a fix for CVE-2026-88983?
- Yes. github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260517162502-504d7797c1e0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88983 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-88983?
- Check whether you run github.com/kubeflow/pipelines (Go) or Kubeflow Pipelines at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260517162502-504d7797c1e0 or later
go get github.com/kubeflow/pipelines@v0.0.0-20260517162502-504d7797c1e0
Technical details
The vulnerability is a server-side request forgery (SSRF) in the pipeline and pipeline-version creation API endpoints. An authenticated caller can inject a user-controlled pipelineURL parameter that the API server fetches without destination validation. The attacker can observe HTTP status codes from requests to internal services, providing a limited oracle for network reconnaissance; however, response body disclosure and credential theft are not established as practical attack outcomes.
Affected products
- Kubeflow Pipelines prior to 2.17.0
Identifiers
- CVE-2026-88983
- GHSA-f7vj-6669-qvv4
Timeline
- 2026-11-05: disclosed