Kubeflow Pipelines: Unauthenticated server-side request forgery in the frontend http/https artifact source via decimal-IP bypass of the…
Affects Kubeflow Pipelines 2.17.3 and earlier, where the frontend http/https artifact source can reach internal HTTP services without authentication. Fixed in 2.18.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.18.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.18.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? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- 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 is affected by a server-side request forgery flaw in its frontend artifact retrieval route, which an attacker can reach remotely without logging in. An attacker can use it to make the server fetch internal HTTP resources and read the responses, and in some deployments this can expose cloud credentials, though that depends on the environment.
Read the original description
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the frontend GET /artifacts/get route accepts source=http or source=https with caller-controlled bucket and key values, and isAllowedResourceName permits an all-digit decimal host that the URL parser converts to an IPv4 address. The default ALLOWED_ARTIFACT_DOMAIN_REGEX and authorization-disabled standalone configuration allow an unauthenticated caller to fetch internal HTTP resources and receive their response body. In the authenticated multi-user configuration, the same destination-validation defect is reachable by a low-privilege tenant with a valid identity and authorized namespace. Cloud credential disclosure depends on reachable metadata services and attached roles, and the issue does not establish IMDSv2 bypass or credential access when metadata is blocked. This issue is fixed in version 2.18.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.18.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- kubeflow pipelines
fixed in 2.18.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-88980
Is CVE-2026-88980 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
What does this mean?
The frontend's http/https artifact source can be made to send requests to internal HTTP services without authentication, and the response body is returned. On EC2-backed deployments with IMDSv1 reachable and an instance profile attached, this can expose the node role's temporary credentials.Source: github.com
Which versions are affected by CVE-2026-88980?
pipelines: before 2.18.0.Source: cve.now feed data
Am I affected, and how do I check?
Kubeflow Pipelines versions 2.17.3 and earlier are affected. The default ALLOWED_ARTIFACT_DOMAIN_REGEX is ^.*$, which allows all domains, so check that setting along with the KFP version. Credential disclosure additionally requires EC2 IMDSv1 to be reachable and an instance profile to be attached.Source: github.com
How do I fix CVE-2026-88980?
Upgrade Kubeflow Pipelines to 2.18.0.Source: github.com