Security Digest · Vulnerability record

CVE-2026-77596: Kubeflow Pipelines API server lacks authorization for shared pipeline uploads

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows.

CVSS 9.6 Critical EPSS 0.4% · p35

Should you act?

Critical, preconditions apply

Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 0.4%, percentile 35: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 35% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Needs an account (low (any account)). Exposure depends on who can log in.
  • Only applies if your dependency tree includes github.com/kubeflow/pipelines (Go) < 0.0.0-20260909234119-62516d8c525f, fixed in 0.0.0-20260909234119-62516d8c525f. Check your lockfile, including transitive dependencies.

What it is

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the multi-user HTTP endpoints POST /apis/v2beta1/pipelines/upload and POST /apis/v2beta1/pipelines/uploadversion call canUploadVersionedPipeline, which returns without SubjectAccessReview when the target namespace is empty while REQUIRENAMESPACEFORPIPELINES defaults to false. A low-privilege tenant can create shared pipelines or inject attacker-controlled versions into existing shared pipelines without the required write permission; if the API server is directly reachable without an authenticating proxy, an unauthenticated caller can exploit the same bypass, while deployments protected by such a proxy do not expose anonymous access. An enabled unpinned recurring run that follows the latest version can then execute the injected specification in another tenant's namespace under that workload's service account, while pinned or embedded-specification runs are not automatically substituted. This issue is fixed in version 2.18.0.

From the GitHub advisory

Summary

In multi-user mode, the Kubeflow Pipelines API server's HTTP multipart upload endpoints (POST /apis/v2beta1/pipelines/upload and POST /apis/v2beta1/pipelines/uploadversion) perform no authorization when the target namespace is empty. The authorization helper canUploadVersionedPipeline returns nil, skipping SubjectAccessReview, whenever the resolved namespace is the empty string (backend/src/apiserver/server/pipelineuploadserver.go:401-403). An empty namespace is how KFP addresses shared, cluster-wide pipelines and is the default whenever the caller omits the namespace query parameter, because REQUIRENAMESPACEFORPIPELINES defaults to false and is unset in every shipped manifest. As a result, an arbitrary low-privilege tenant (or, when the API server is reachable, an unauthenticated caller) can create cluster-shared pipelines and inject new versions into existing shared pipelines, replacing the container image, command, and args that other tenants execute. The gRPC sibling for the same write, canAccessPipeline, instead remaps the empty namespace to the system namespace and authorizes, with a comment stating shared-pipeline writes "must still be authorized". That confirms this is an omission, not intended behavior.

Description

uploadPipeline and uploadPipelineVersion both build a ResourceAttributes{Verb: create} and delegate the access decision to canUploadVersionedPipeline:

When the namespace is empty (a shared/cluster-wide pipeline, or simply an upload with no namespace parameter), the function returns at line 401-403 and IsAuthorized is never reached.

Weakness type: CWE-639, CWE-862.

Product: github.com/kubeflow/pipelines (Go) · Assigned by: GitHub_M · Published: 2026-11-05

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Gogithub.com/kubeflow/pipelines< 0.0.0-20260909234119-62516d8c525f0.0.0-20260909234119-62516d8c525f
VendorProductAffected versions (per CVE record)
kubeflowpipelines< 2.18.0

Severity scores

Scored byCVSSScoreVector
GitHub_M3.19.6 CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
GitHub3.19.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: low (any account)
  • User interaction: none
  • Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-11-21): 0.40% probability of exploitation activity in the next 30 days; percentile 35.

Timeline

  • — CVE record published by GitHub_M
  • — GitHub-reviewed advisory GHSA-rjr3-43j3-4q8g published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-rjr3-43j3-4q8g github.com
  2. CVE.org record CVE-2026-77596 cve.org
  3. NVD entry CVE-2026-77596 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com

Critical Go advisories · Today’s Security Digest