Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Kubeflow Pipelines: Pipeline archive upload allows decompression bomb to exhaust server memory

CVE-2026-118761GHSA-8fmv-6rg5-5924

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/kubeflow/pipelines

    Affected
    < 0.0.0-20260831164314-ba9ae72cc860>= 1.7.0-alpha.3, <= 1.7.0-alpha.3
    Fixed in
    0.0.0-20260831164314-ba9ae72cc860

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-118761: 0.50% estimated exploitation activity in the next 30 days; percentile 42.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The Kubeflow Pipelines API server decompresses uploaded pipeline archives without adequately bounding expanded data in affected versions. A small ZIP or gzip-compressed tar archive can consume disproportionately large amounts of memory while the server locates or reads the pipeline file, potentially exhausting API-server resources and interrupting service. 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 to trigger the issue. External authentication and network controls can restrict reachability. URL-import handlers authorize before fetching and decompressing a remote archive. The amount of expansion needed to exhaust memory depends on deployment resource limits and concurrent activity; no particular archive is guaranteed to crash every deployment.

Remediation Upgrade the API server to **Kubeflow…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-8fmv-6rg5-5924

  2. Revision 1 · created ·

    Published from ghsa record GHSA-8fmv-6rg5-5924

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-118761

Advisory: Kubeflow Pipelines: Pipeline archive upload allows decompression bomb to exhaust server memory
IDs: CVE-2026-118761, GHSA-8fmv-6rg5-5924
Record: https://patchnext.com/advisories/cve-2026-118761 (revision 2, source checked 31 Oct 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/kubeflow/pipelines 0.0.0-20260831164314-ba9ae72cc860. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kubeflow/pipelines: affected < 0.0.0-20260831164314-ba9ae72cc860; >= 1.7.0-alpha.3, <= 1.7.0-alpha.3; fixed in 0.0.0-20260831164314-ba9ae72cc860

## Suggested inspection (read-only)
- Go github.com/kubeflow/pipelines: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kubeflow/pipelines.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8fmv-6rg5-5924 (GitHub-reviewed advisory GHSA-8fmv-6rg5-5924 lists affected ranges: Go github.com/kubeflow/pipelines >=0 =1.7.0-alpha.3 <=1.7.0-alpha.3)
- Verified: https://osv.dev/vulnerability/GHSA-8fmv-6rg5-5924 (OSV record GHSA-8fmv-6rg5-5924 lists affected ranges: Go github.com/kubeflow/pipelines >=0 =1.7.0-alpha.3 <=1.7.0-alpha.3)

Commands are suggestions: review each one before running it.

Loading voting…