Quick answers
- Is CVE-2026-88986 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88986 being exploited in the wild.
- How severe is CVE-2026-88986?
- Medium severity, with a CVSS score of 6.1, published 5 November 2026.
- Which products and versions are affected?
- github.com/kubeflow/pipelines (Go) < 0.0.0-20251010122814-fedc25e3f725, SEMVER:introduced=0,fixed=0.0.0-20251010122814-fedc25e3f725; Kubeflow Pipelines before 2.15.0.
- Is there a fix for CVE-2026-88986?
- Yes. github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20251010122814-fedc25e3f725 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88986 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-88986?
- 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-20251010122814-fedc25e3f725 or later
go get github.com/kubeflow/pipelines@v0.0.0-20251010122814-fedc25e3f725
Technical details
Reflected XSS vulnerability in frontend routes /pipeline/k8s/pod and /pipeline/k8s/pod/events due to unsanitized podname and podnamespace query parameters being included in HTML-capable error responses. An unauthenticated attacker can craft a malicious link containing script payloads that executes in the frontend origin when clicked by a user with deployment authentication and route access. Cookie disclosure risk depends on cookie attributes; no server-side code execution or availability impact established.
Affected products
- Kubeflow Pipelines before 2.15.0
Identifiers
- CVE-2026-88986
- GHSA-g3qx-frcg-j979
Timeline
- 2026-11-05: disclosed