Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

Kubeflow Pipelines: SQL injection through unvalidated pagination tokens in Kubeflow Pipelines API server

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/kubeflow/pipelines 0.0.0-20260403210607-ac3a4c65677a), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-88985: 0.26% estimated exploitation activity in the next 30 days; percentile 17.82 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Kubeflow Pipelines API server does not sufficiently validate SQL identifier fields decoded from the `page_token` pagination parameter. Client-controlled fields can reach SQL query construction, allowing SQL injection through list APIs. This advisory consolidates the original pipeline-listing report and the later run-listing report in GHSA-mhpc-2x8q-2vp9. Their contributions and chronology are distinguished below.

Impact and prerequisites An attacker able to invoke an affected list API may read data accessible to the API server's database account, including data belonging to other namespaces. The original report demonstrated database read access through an authenticated Kubeflow deployment. Authentication and authorization requirements depend on deployment configuration. In multi-user deployments, the attacker must pass the applicable endpoint authorization checks. A single-user deployment…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-r4mx-2gr2-8277

  2. Revision 1 · created ·

    Published from ghsa record GHSA-r4mx-2gr2-8277

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-88985

Advisory: Kubeflow Pipelines: SQL injection through unvalidated pagination tokens in Kubeflow Pipelines API server
IDs: CVE-2026-88985, GHSA-r4mx-2gr2-8277
Record: https://patchnext.com/advisories/cve-2026-88985 (revision 2, source checked 10 Nov 2026, 06:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/kubeflow/pipelines 0.0.0-20260403210607-ac3a4c65677a. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kubeflow/pipelines: affected < 0.0.0-20260403210607-ac3a4c65677a; fixed in 0.0.0-20260403210607-ac3a4c65677a

## Suggested inspection (read-only)
- Go github.com/kubeflow/pipelines: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kubeflow/pipelines.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r4mx-2gr2-8277 (GitHub-reviewed advisory GHSA-r4mx-2gr2-8277 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260403210607-ac3a4c65677a)
- Verified: https://osv.dev/vulnerability/GHSA-r4mx-2gr2-8277 (OSV record GHSA-r4mx-2gr2-8277 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260403210607-ac3a4c65677a (fixed))

Commands are suggestions: review each one before running it.

Loading voting…