Read the docs
TI-2026-85700 Aliases CVE-2026-88982

Cross-tenant cache poisoning in Kubeflow Pipelines execution cache

Priority LOW 23CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Partial Red Hat: 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-345.

Summary

Kubeflow Pipelines before 2.18.0 is affected. The legacy V1 execution cache builds its lookup key without the Kubernetes namespace, which lets tenants share cache entries (CWE-639). In multi-user deployments, a tenant with workload-submission privileges can read another namespace's cached outputs or seed outputs that are substituted into a later step.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the legacy V1/raw-Argo execution cache mutating webhook and cache-server storage path hash selected template fields without the Kubernetes namespace, use the key alone for lookups and duplicate checks, and trust the mutable pipelines.kubeflow.org/execution_cache_key annotation when publishing outputs. In multi-user deployments where tenant namespaces share the cache service, a tenant with workload-submission privileges can read another namespace's cached outputs or seed matching outputs that are substituted into a later step. Standard KFP V2 component pods bypass this cache, matching requires the selected template fields and staleness policy, and arbitrary code execution or service availability impact is not established. This issue is fixed in version 2.18.0.

Why it matters now

EPSS 0.0015 4th percentileScored 2026-11-07
Fix Partial pipelines (kubeflow): 2.18.0Red Hat: 1 without a fix

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
kubeflowpipelinesbefore 2.18.02.18.0Patch availableCNA
  • pipelines Vendorkubeflow Affected before 2.18.0 Fixed in 2.18.0 Patch available CNA

Remediation

Upgrade Kubeflow Pipelines to version 2.18.0, which fixes this issue. The sources list no fixed version for Red Hat OpenShift AI (RHOAI).

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA pipelines (kubeflow) Fixed in 2.18.0

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat OpenShift AI (RHOAI)Affected—

Timeline

  1. 2026-11-05 Threatist record created from CVE-2026-88982
  2. 2026-11-06 Affected versions changed · Red Hat
  3. 2026-11-06 CVSS score added · Red Hat
  4. 2026-11-07 Priority changed: MEDIUM → LOW

References

Other 4

  • TI-2026-39556 Improper access control in kubeflow pipelines CVSS 3.1CRITICAL 10.0
  • TI-2024-05160 ReDoS in kubeflow/kubeflow CVSS 3.1HIGH 7.5
  • TI-2026-34822 Kubeflow Community Distribution: Overly Permissive Istio Permissions Allows Kubeflow Authorization Token Stealing CVSS 3.1HIGH 8.0
  • TI-2026-85696 Server-side request forgery in Kubeflow Pipelines TensorBoard proxy CVSS 3.1MEDIUM 5.8
  • TI-2026-73437 Server-side request forgery in Kubeflow Model Registry leaks tokens CVSS 4.0HIGH 7.1
  • TI-2026-85698 Server-side request forgery in Kubeflow Pipelines artifact endpoints CVSS 3.1HIGH 8.6
See all 19 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences