Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach multipart upload endpoint
-
DeliverySubmit small compressed archive bomb
-
ExploitServer decompresses before authorization
-
ExecutionMemory expands beyond resource limits
-
ImpactAPI server resource exhaustion / service interruption
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Compression ratio limits
|
| Exploitation Conditions | Exploitation requires network reachability to the API server's multipart pipeline-upload or pipeline-version-upload endpoints, which decompress the archive before namespace authorization - so a reachable caller does not need a successful pipeline-create authorization decision. The attack uses a crafted small ZIP or gzip-compressed tar archive whose expansion is disproportionate to its compressed size. What LIMITS exploitation: the URL-import handlers are NOT vulnerable to the pre-auth path because they authorize before fetching and decompressing; external authentication and network controls in front of the API server can restrict who reaches the upload endpoints; and success is not guaranteed by any single archive because the expansion needed depends on the deployment's resource limits and concurrent activity. Affected versions are Kubeflow Pipelines through 2.17.3; the issue is fixed in 2.18.0. |
| Impact | This is a credible but bounded availability issue rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5 HIGH) describes a network-reachable, low-complexity attack affecting availability only, with no confidentiality or integrity impact. The vuln.today decision label is 'this_week', consistent with a serious DoS that is not under active exploitation. No EPSS score was supplied, no KEV listing is present, and no SSVC fields were provided, so exploitation-probability and automatability signals are missing from the input and cannot be weighed. The key amplifier is that multipart pipeline and pipeline-version upload processing decompresses the archive BEFORE namespace authorization, so a caller who can reach those endpoints does not need a successful pipeline-create authorization decision - this is what justifies PR:N. The main mitigating realities, stated by the vendor, are that external authentication and network controls can restrict reachability, that URL-import handlers authorize before fetching/decompressing, and that no particular archive is guaranteed to crash every deployment because the expansion needed depends on deployment resource limits and concurrent activity. Net: treat as a real priority for internet- or multi-tenant-exposed Kubeflow Pipelines API servers, but a lower-urgency patch where the upload endpoints already sit behind strong authentication and network segmentation. |
| Exploit ScenarioDerived | An attacker who can reach the Kubeflow Pipelines API server's multipart pipeline or pipeline-version upload endpoint submits a small ZIP or gzip-compressed tar 'decompression bomb'. Because decompression happens before namespace authorization, the server expands the archive into memory while locating or reading the pipeline file, consuming disproportionate memory and potentially exhausting API-server resources and interrupting service. No public exploit identified at time of analysis; the referenced links are the vendor advisory, fix PRs, and commits, not a working exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Memory exhaustion in the Kubeflow Pipelines API server (versions through 2.17.3) lets a network-reachable, unauthenticated caller submit a small ZIP or gzip-compressed tar archive that expands disproportionately while the server locates or reads the pipeline file, potentially exhausting API-server memory and interrupting service. The multipart pipeline and pipeline-version upload endpoints decompress the archive before namespace authorization, so no successful pipeline-create decision is required - although external authentication and network controls in front of the API server can restrict reachability, and the URL-import handlers authorize before fetching remote archives and are therefore not on this pre-authorization path. No public exploit code and no confirmed active exploitation were identified at time of analysis; the impact is bounded to availability (C:N/I:N/A:H) and no single archive is guaranteed to exhaust every deployment, since the expansion needed depends on resource limits and concurrent activity. Fixed in 2.18.0.
RemediationAI
Vendor-released patch: upgrade the API server to Kubeflow Pipelines 2.18.0 (https://github.com/kubeflow/pipelines/releases/tag/2.18.0), which contains the archive-bounding fixes from PR #14171 (https://github.com/kubeflow/pipelines/pull/14171) and the strengthened tar traversal budget including metadata and skipped entries from PR #14186 (https://github.com/kubeflow/pipelines/pull/14186), with commits 1121d9a081fdf9e2107c39abb2cd8947727c6953 and ba9ae72cc860e3afbea232185e4132fc2896cac5. The 2.18 release also adds configurable upload and specification limits, so operators should review the shipped settings against their resource budget; note that the vendor states these controls do not establish general HTTP-body, temporary-disk, concurrency or CPU limits. Until upgrading, restrict access to the pipeline upload and URL-import endpoints and apply deployment-level request and resource controls in front of the API server, recognizing that a compressed upload-size limit alone does not prevent decompression amplification; deployment-level controls carry the trade-off of throttling legitimate large or concurrent pipeline uploads.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-409 (Improper Handling of Highly Compressed Data / decompression bomb) in the Go-based kfp-api-server component (CPE cpe:2.3:a:kubeflow:pipelines:*:*:*:*:*:*:*:*). The pre-fix code in backend/src/apiserver/server/util.go read decompressed content with unbounded io.ReadAll calls: DecompressPipelineZip pulled the selected entry from archive/zip through a raw io.ReadAll, and DecompressPipelineTarball fed compress/gzip into archive/tar and read the target member without any ceiling on total expanded bytes. Because the ceiling was applied to the compressed upload only, a highly compressible payload could expand far past the intended MaxFileLength while the server searched for and read the pipeline file. The upstream fix replaces these with io.LimitReader(fileReader, MaxFileLength+1) on the raw read and a LimitedReader wrapping the gzip stream with a traversal budget of maxFileLength + 1MB to cover tar headers, padding and skipped members, checking remaining budget after each entry and rejecting output above maxFileLength; the exported helpers retain a 32MB default for backwards compatibility. The trigger requires the multipart upload path, which decompresses before namespace authorization - the URL-import path authorizes first, so the pre-authorization exposure is specific to the upload endpoints. The advisory notes these controls bound pipeline-archive amplification and do not establish general HTTP-body, temporary-disk, concurrency or CPU limits.
Know when Kubeflow gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Multipart upload decompresses before namespace authorization so PR:N and AC:L; impact is availability-only (A:H) with no confidentiality or integrity effect.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the API server decompressed uploaded pipeline archives without adequately bounding expanded data while locating or reading the pipeline file. A small ZIP or gzip-compressed tar archive can consume disproportionately large memory and exhaust API-server resources. Multipart pipeline and pipeline-version upload processing performs decompression before namespace authorization, so a reachable caller does not need a successful pipeline-create authorization decision. URL-import handlers authorize before fetching and decompressing a remote archive. The amount of expansion required to interrupt service depends on deployment resource limits and concurrent activity, and no specific archive is guaranteed to crash every deployment. This issue is fixed in version 2.18.0.
Technical POC Analysis
CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) - a classic decompression bomb in the Kubeflow Pipelines API server.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
CVE-2026-118761 is a high-severity memory exhaustion vulnerability in Kubeflow Pipelines API server (through 2.17.3) that allows an unauthenticated network attacker to submit a small compressed archive, causing disproportionate memory use and potential service disruption. This affects any organization relying on Kubeflow Pipelines for ML workflows, where availability is critical; leadership should care because exploitation could interrupt pipeline operations and degrade productivity.
Restrict network access to the Kubeflow Pipelines API server to trusted users and networks; enforce external authentication (e.g., OAuth proxy or service mesh mTLS) to block unauthenticated requests; apply resource limits (memory and CPU) to API server pods; monitor for unusual memory spikes or large uploads and alert accordingly.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
kubeflow/kubeflow is vulnerable to a Regular Expression Denial of Service (ReDoS) attack due to inefficient regular expr
Server-Side Request Forgery (SSRF) in kubeflow/kubeflow. Rated medium severity (CVSS 6.5), this vulnerability is remotel
Cross-site Scripting (XSS) - Reflected in kubeflow/kubeflow. Rated medium severity (CVSS 6.1), this vulnerability is rem
Server-side request forgery in the Kubeflow Pipelines frontend server (prior to 2.17.0) lets any unauthenticated network
Authorization token theft in Kubeflow Community Distribution before 26.03-rc.1 lets a low-privileged tenant hijack other
Path traversal in the Kubeflow Pipelines volume artifact handler (versions through 2.17.3, fixed in 2.18.0) lets a remot
Unauthorized log disclosure in the Kubeflow Pipelines API server allows a caller who can reach the backend and supply a
Kubeflow Model Registry through 0.3.17 allows an authenticated namespace user with permission to create InferenceService
There exists a stored XSS Vulnerability in Kubeflow Pipeline View web UI. Rated high severity (CVSS 7.1), this vulnerabi
Cross-tenant artifact disclosure in the Kubeflow Pipelines frontend (kfp-frontend) lets an authenticated user who can re
EUVD-2026-113219
GHSA-8fmv-6rg5-5924
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB