Server-side request forgery in Kubeflow Pipelines artifact fetching
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-918 and the CVSS impact.
Summary
In Kubeflow Pipelines before 2.18.0, the frontend GET /artifacts/get route accepts http and https sources, and a decimal IP host bypasses its bucket validator (CWE-918). An unauthenticated attacker can make the server fetch internal HTTP resources and read the response bodies in standalone mode with authorization disabled. A low-privilege tenant with a valid identity and authorized namespace can do the same in multi-user setups. Cloud credential exposure depends on reachable metadata services and attached roles.
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
Description from the CNA
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
Upgrade Kubeflow Pipelines to version 2.18.0, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
- Fix · CNA pipelines (kubeflow) Fixed in 2.18.0
Timeline
- 2026-11-05 Threatist record created from CVE-2026-88980
- 2026-11-07 Priority changed: MEDIUM → LOW
References
More kubeflow vulnerabilities
- TI-2026-39556 Improper access control in kubeflow pipelines CVSS 3.1CRITICAL 10.0
- TI-2024-05160 ReDoS in kubeflow/kubeflow CVSS 3.1HIGH 7.5
- TI-2026-34822 Kubeflow Community Distribution: Overly Permissive Istio Permissions Allows Kubeflow Authorization Token Stealing CVSS 3.1HIGH 8.0
- TI-2026-85696 Server-side request forgery in Kubeflow Pipelines TensorBoard proxy CVSS 3.1MEDIUM 5.8
- TI-2026-73437 Server-side request forgery in Kubeflow Model Registry leaks tokens CVSS 4.0HIGH 7.1
- TI-2026-85698 Server-side request forgery in Kubeflow Pipelines artifact endpoints CVSS 3.1HIGH 8.6
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences