Is CVE-2026-88985 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-88985 being exploited in the wild.

How severe is CVE-2026-88985?

Medium severity, with a CVSS score of 6.5, published 5 November 2026.

Which products and versions are affected?

github.com/kubeflow/pipelines (Go) < 0.0.0-20260403210607-ac3a4c65677a, SEMVER:introduced=0,fixed=0.0.0-20260403210607-ac3a4c65677a; Kubeflow Pipelines before 2.17.0.

Is there a fix for CVE-2026-88985?

Yes. github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260403210607-ac3a4c65677a or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-88985 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-88985?

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.

CVE-2026-88985: Kubeflow Pipelines SQL injection in pageToken parameter

Q: Is there a fix for CVE-2026-88985?

Yes. github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260403210607-ac3a4c65677a or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-88985 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-88985?

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.

CVE-2026-88985 · Severity: medium · CVSS 6.5 · Published 2026-11-05

Kubeflow Pipelines is a platform for building and deploying machine learning workflows. The API server's list endpoints trust unvalidated database field names from a base64-encoded pageToken parameter, allowing attackers to inject SQL code and read data across database namespaces without requiring authentication to specific pipelines. An attacker can invoke list APIs with a crafted pageToken to extract sensitive data available to the API server's database account.

Technologies: github.com/kubeflow/pipelines (Go), Kubeflow Pipelines. Vendors: Go, Kubeflow.

Quick answers

Is CVE-2026-88985 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-88985 being exploited in the wild.
How severe is CVE-2026-88985?: Medium severity, with a CVSS score of 6.5, published 5 November 2026.
Which products and versions are affected?: github.com/kubeflow/pipelines (Go) < 0.0.0-20260403210607-ac3a4c65677a, SEMVER:introduced=0,fixed=0.0.0-20260403210607-ac3a4c65677a; Kubeflow Pipelines before 2.17.0.
Is there a fix for CVE-2026-88985?: Yes. github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260403210607-ac3a4c65677a or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-88985 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-88985?: 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-20260403210607-ac3a4c65677a or later
```
go get github.com/kubeflow/pipelines@v0.0.0-20260403210607-ac3a4c65677a
```

Technical details

The vulnerability is a SQL injection flaw in the pageToken parameter handling of Kubeflow Pipelines' list APIs (v1beta1 and v2beta1). The API server deserializes base64-encoded JSON tokens containing database field names (KeyFieldName, SortByFieldName, ModelName) and directly concatenates them into SQL WHERE and ORDER BY clauses without validation. An attacker who can invoke any pipeline or run list API can inject arbitrary SQL through these identifier fields, including via metric sort names, to read unauthorized data. The fix (version 2.17.0) adds a validateIdentifierName() function with a strict allowlist regex and applies it to all identifier fields before SQL construction.

Affected products

Kubeflow Pipelines before 2.17.0

Identifiers

CVE-2026-88985
GHSA-r4mx-2gr2-8277

Timeline

2026-11-05: disclosed
2026-04-03: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.