Is CVE-2026-88982 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-88982 being exploited in the wild.

How severe is CVE-2026-88982?

Medium severity, with a CVSS score of 5.4, published 5 November 2026.

Which products and versions are affected?

github.com/kubeflow/pipelines (Go) < 0.0.0-20260910172610-620d0cc89ae0, SEMVER:introduced=0,fixed=0.0.0-20260910172610-620d0cc89ae0; Kubeflow Pipelines before 2.18.0.

How is CVE-2026-88982 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-88982?

Check whether you run github.com/kubeflow/pipelines (Go) or Kubeflow Pipelines at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-88982: Kubeflow Pipelines cross-tenant cache isolation in execution cache

Q: Is there a fix for CVE-2026-88982?

Yes. github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260910172610-620d0cc89ae0 or later. Until then: Operators should stop old cache-server replicas before deploying the fixed version, coordinate webhook downtime with workload submissions, and allow the namespace migration to complete before resuming submissions. Mixed old and new cache replicas do not provide the namespace isolation guarantee. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-88982 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-88982?

Check whether you run github.com/kubeflow/pipelines (Go) or Kubeflow Pipelines at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-88982 · Severity: medium · CVSS 5.4 · Published 2026-11-05

Kubeflow Pipelines is a machine learning workflow platform that executes containerized pipeline steps in Kubernetes clusters. In multi-tenant environments before version 2.18.0, the legacy execution cache failed to properly isolate outputs between different tenants, allowing one tenant to access another tenant's cached workflow results or inject poisoned cache entries into another tenant's pipelines.

Technologies: github.com/kubeflow/pipelines (Go), Kubeflow Pipelines. Vendors: Go, Kubeflow.

Quick answers

Is CVE-2026-88982 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-88982 being exploited in the wild.
How severe is CVE-2026-88982?: Medium severity, with a CVSS score of 5.4, published 5 November 2026.
Which products and versions are affected?: github.com/kubeflow/pipelines (Go) < 0.0.0-20260910172610-620d0cc89ae0, SEMVER:introduced=0,fixed=0.0.0-20260910172610-620d0cc89ae0; Kubeflow Pipelines before 2.18.0.
Is there a fix for CVE-2026-88982?: Yes. github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260910172610-620d0cc89ae0 or later. Until then: Operators should stop old cache-server replicas before deploying the fixed version, coordinate webhook downtime with workload submissions, and allow the namespace migration to complete before resuming submissions. Mixed old and new cache replicas do not provide the namespace isolation guarantee. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-88982 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-88982?: Check whether you run github.com/kubeflow/pipelines (Go) or Kubeflow Pipelines at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/kubeflow/pipelines (Go): upgrade to 0.0.0-20260910172610-620d0cc89ae0 or later
```
go get github.com/kubeflow/pipelines@v0.0.0-20260910172610-620d0cc89ae0
```

Operators should stop old cache-server replicas before deploying the fixed version, coordinate webhook downtime with workload submissions, and allow the namespace migration to complete before resuming submissions. Mixed old and new cache replicas do not provide the namespace isolation guarantee.

Technical details

The legacy V1/raw-Argo execution cache computed its storage keys using only template container fields, omitting the Kubernetes namespace, enabling cross-tenant collision when identical pipeline steps ran in different tenants' namespaces. A tenant with workload submission privileges could read cached outputs written by another tenant or seed malicious cache entries that would be substituted into another tenant's later workflow steps. The fix, deployed in version 2.18.0, incorporates the namespace into the cache key hash and enforces namespace ownership on both read and write paths.

Affected products

Kubeflow Pipelines before 2.18.0

Identifiers

CVE-2026-88982
GHSA-2xwh-426q-42c5

Timeline

2026-11-05: disclosed
2026-09-10: patched: Fix merged to master branch

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.