Kubeflow Pipelines API server lacks authorization for shared pipeline uploads
CVE-2026-77596GHSA-rjr3-43j3-4q8g
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/kubeflow/pipelines 0.0.0-20260909234119-62516d8c525f), redeploy, then verify what is actually installed.
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.
Affected packages
Go github.com/kubeflow/pipelines
- Affected
- < 0.0.0-20260909234119-62516d8c525f
- Fixed in
- 0.0.0-20260909234119-62516d8c525f
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rjr3-43j3-4q8g lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260909234119-62516d8c525f
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-rjr3-43j3-4q8g lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260909234119-62516d8c525f (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- EPSS
- CVE-2026-77596: 0.25% estimated exploitation activity in the next 30 days; percentile 16.50 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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/upload_version`) 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/pipeline_upload_server.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 `REQUIRE_NAMESPACE_FOR_PIPELINES` 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-rjr3-43j3-4q8g
- Revision 1 · created ·
Published from ghsa record GHSA-rjr3-43j3-4q8g
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-77596 Advisory: Kubeflow Pipelines API server lacks authorization for shared pipeline uploads IDs: CVE-2026-77596, GHSA-rjr3-43j3-4q8g Record: https://patchnext.com/advisories/cve-2026-77596 (revision 2, source checked 10 Nov 2026, 06:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/kubeflow/pipelines 0.0.0-20260909234119-62516d8c525f. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/kubeflow/pipelines: affected < 0.0.0-20260909234119-62516d8c525f; fixed in 0.0.0-20260909234119-62516d8c525f ## Suggested inspection (read-only) - Go github.com/kubeflow/pipelines: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## 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-rjr3-43j3-4q8g (GitHub-reviewed advisory GHSA-rjr3-43j3-4q8g lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260909234119-62516d8c525f) - Verified: https://osv.dev/vulnerability/GHSA-rjr3-43j3-4q8g (OSV record GHSA-rjr3-43j3-4q8g lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260909234119-62516d8c525f (fixed)) Commands are suggestions: review each one before running it.
Loading voting…