Zero Radar
← feed
HighVulnerabilityCVE-2026-118761updated 30 Oct 2026, 23:14 UTC

Kubeflow Pipelines API server can run out of memory from crafted pipeline archives

A small, specially crafted zip or tar.gz file uploaded as a pipeline can expand into a huge amount of data in the server's memory, which can slow or crash the service. Uploads can be processed before permission checks, so unauthorized calle

Fix available · out Official, 2 sources
SeverityHighCVSS 7.5 of 10
Being exploited?UnclearNo reports either way yet
Fix available?YesKubeflow Pipelines 2.18.0; go/github.com/kubeflow/pipelines 0.0.0-20260831164314-ba9ae72cc860. · since 30 Oct 2026
How sure is this?Official, 2 sourcesBacked by an official source

How the attack works simplified

  1. 1Crafted archiveSmall ZIP or tar.gz file prepared
  2. 2Upload requestSent to pipeline upload endpoint
  3. 3Server decompressesExpansion runs before permission check
  4. 4Memory exhaustedExpanded data overwhelms API server
  5. ResultAPI server service is interrupted

What happened

Kubeflow Pipelines API server decompresses uploaded pipeline archives (ZIP or gzip tar) without adequately bounding expanded data, enabling memory exhaustion via decompression amplification. Multipart pipeline and pipeline-version uploads decompress before namespace authorization.

Why it is dangerous: A reachable caller can interrupt service for the whole Kubeflow Pipelines API server, affecting all users of that deployment. Exact impact depends on resource limits and concurrent activity.

Are you affected?

You are affected if you run Kubeflow Pipelines API server version 2.17.3 or earlier (or a go/github.com/kubeflow/pipelines build before 0.0.0-20260831164314-ba9ae72cc860) and its upload endpoints are reachable.

Package / productAffected versionsFixed in
github.com/kubeflow/pipelines · go< 0.0.0-20260831164314-ba9ae72cc8600.0.0-20260831164314-ba9ae72cc860
github.com/kubeflow/pipelines · go= 1.7.0-alpha.3no fix yet

What to do

  1. Upgrade the Kubeflow Pipelines API server to 2.18.0 or later
  2. Until upgraded, restrict access to pipeline upload and URL-import endpoints
  3. Apply deployment-level request and resource limits, and review the new 2.18 upload and specification limit settings

Timeline

  1. 29 Oct 2026, 17:18 UTC
    Publicly disclosed
  2. 29 Oct 2026, 17:18 UTC
    Reported by NVD · NVD
  3. 29 Oct 2026, 17:20 UTC
    Picked up by Zero Radar
  4. 30 Oct 2026, 23:14 UTC
    GitHub Advisory reported on it · GitHub Advisory
  5. 30 Oct 2026, 23:14 UTC
    Fixed version published: github.com/kubeflow/pipelines 0.0.0-20260831164314-ba9ae72cc860 · GitHub Advisory

Sources 2 reports, oldest first

Official vendor, government CERT or advisory database

Technical details

ID
CVE-2026-118761 · GHSA-8fmv-6rg5-5924
CVSS
7.5 / 10
Disclosed
29 Oct 2026, 17:18 UTC
On Zero Radar
29 Oct 2026, 17:20 UTC (2 min after disclosure)
Last change
30 Oct 2026, 23:14 UTC

The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works

Kubeflow Pipelines API server can run out of memory from crafted pipeline archives · Zero Radar