Kubeflow Pipelines: SQL injection through unvalidated pagination tokens in Kubeflow Pipelines API server
- Exploited
- No known exploitation
- Fix
- Fixed in 2.17.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.17.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Kubeflow Pipelines, a platform for building and deploying machine learning workflows, has a SQL injection flaw in its API server's handling of pagination tokens. An attacker who can reach the API over the network and has low-privilege login credentials could read data available to the API server's database account across namespaces, though database modification has not been established.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.17.0, the API server trusts structural SQL identifier fields decoded from the base64-encoded JSON page_token parameter before constructing list queries. An attacker who can invoke an affected pipeline or run list API can inject through KeyFieldName or SortByFieldName, including v1beta1 and v2beta1 run-listing metric paths, and read data available to the API server database account across namespaces. Database modification is not established. This issue is fixed in version 2.17.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.17.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- kubeflow pipelines
fixed in 2.17.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-88985
Is CVE-2026-88985 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-88985?
pipelines: before 2.17.0.Source: cve.now feed data
How do I fix CVE-2026-88985?
Upgrade to a fixed version: 2.17.0.Source: cve.now feed data