Kubeflow Pipelines: Cross-tenant execution-cache poisoning / output substitution via a namespace-blind cache key in the cache webhook (multi-user)
CVE-2026-88982GHSA-2xwh-426q-42c5
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-20260910172610-620d0cc89ae0), 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-20260910172610-620d0cc89ae0
- Fixed in
- 0.0.0-20260910172610-620d0cc89ae0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2xwh-426q-42c5 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260910172610-620d0cc89ae0
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-2xwh-426q-42c5 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260910172610-620d0cc89ae0 (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
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- EPSS
- CVE-2026-88982: 0.15% estimated exploitation activity in the next 30 days; percentile 4.20 (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 The legacy Kubeflow Pipelines V1/raw-Argo execution cache does not separate cached results by Kubernetes namespace. In multi-user deployments where tenants share the cache service, a tenant can receive another tenant's cached outputs or seed outputs that are subsequently substituted into another tenant's step. This affects the Argo-template cache mutating webhook and its cache-server storage path. Standard KFP V2 component pods bypass this webhook cache; the separate V2 cache implementation is outside this advisory's scope.
Affected deployments and impact The issue requires multiple tenant namespaces sharing the legacy cache service, cache-enabled V1/raw-Argo steps, and cache entries that satisfy the configured staleness policy. The standard multi-user configuration watches pods across namespaces. A tenant able to submit a step with the same cache-relevant template fields as another tenant's step can: - Read cached step outputs originally produced in another namespace.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-2xwh-426q-42c5
- Revision 1 · created ·
Published from ghsa record GHSA-2xwh-426q-42c5
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-88982 Advisory: Kubeflow Pipelines: Cross-tenant execution-cache poisoning / output substitution via a namespace-blind cache key in the cache webhook (multi-user) IDs: CVE-2026-88982, GHSA-2xwh-426q-42c5 Record: https://patchnext.com/advisories/cve-2026-88982 (revision 2, source checked 10 Nov 2026, 06:35 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.4) 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-20260910172610-620d0cc89ae0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/kubeflow/pipelines: affected < 0.0.0-20260910172610-620d0cc89ae0; fixed in 0.0.0-20260910172610-620d0cc89ae0 ## 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-2xwh-426q-42c5 (GitHub-reviewed advisory GHSA-2xwh-426q-42c5 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260910172610-620d0cc89ae0) - Verified: https://osv.dev/vulnerability/GHSA-2xwh-426q-42c5 (OSV record GHSA-2xwh-426q-42c5 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20260910172610-620d0cc89ae0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…