CVE-2026-118761: kubeflow pipelines · Data Amplification
Affects kubeflow pipelinesSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 2.18.0 soon.
Data as of 29 Oct 2026, 18:49 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 2.18.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade pipelines and kubeflow/pipelines to 2.18.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| kubeflowpipelines | Affected
| Fixed in
|
GitHubkubeflow/pipelinespkg:github/kubeflow/pipelinesOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Kubeflow Pipelines to version 2.18.0 or later, where this issue is fixed. No other mitigation is required as the fix bounds decompression resource usage and enforces authorization before decompression in all upload paths.
Description
Kubeflow Pipelines prior to version 2.18.0 contains a vulnerability where the API server decompresses uploaded pipeline archives without properly limiting the expanded data size. This can lead to excessive memory consumption and resource exhaustion, potentially causing a denial of service. The vulnerability arises because decompression occurs before namespace authorization during multipart uploads, allowing unauthenticated callers to trigger resource exhaustion. The issue is fixed in version 2.18.0.
References
- github.com/kubeflow/pipelines/security/advisories/GHSA-8fmv-6rg5-5924 (opens in a new tab)
- github.com/kubeflow/pipelines/pull/14171 (opens in a new tab)
- github.com/kubeflow/pipelines/pull/14186 (opens in a new tab)
- github.com/kubeflow/pipelines/commit/1121d9a081fdf9e2107c39abb2cd8947727c6953 (opens in a new tab)
- github.com/kubeflow/pipelines/commit/ba9ae72cc860e3afbea232185e4132fc2896cac5 (opens in a new tab)
- github.com/kubeflow/pipelines/releases/tag/2.18.0 (opens in a new tab)