Is CVE-2026-118760 exploited in the wild?

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

How severe is CVE-2026-118760?

Medium severity, with a CVSS score of 6.5, published 29 October 2026.

Which products and versions are affected?

Kubeflow Pipelines 0.5.1 to 2.16.x.

How is CVE-2026-118760 attacked?

It is attacked over the network.

Am I affected by CVE-2026-118760?

Check whether you run 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-118760: Kubeflow Pipelines authorization bypass in artifact access

CVE-2026-118760 · Severity: medium · CVSS 6.5 · Published 2026-10-29

Kubeflow Pipelines is a platform for building and deploying machine learning workflows. In multi-user deployments, the frontend artifact routes did not properly verify that authenticated users had authorization to access other tenants' namespaces, allowing an attacker to read sensitive data like datasets, models, and pipeline outputs belonging to other users.

Technologies: Kubeflow Pipelines. Vendors: Kubeflow.

Quick answers

Is CVE-2026-118760 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118760 being exploited in the wild.
How severe is CVE-2026-118760?: Medium severity, with a CVSS score of 6.5, published 29 October 2026.
Which products and versions are affected?: Kubeflow Pipelines 0.5.1 to 2.16.x.
Is there a fix for CVE-2026-118760?: Yes: fixed in 2.17.0. Until then: Restrict network access to the Kubeflow Pipelines frontend to authorized users only. The fix is available in version 2.17.0; upgrade as soon as possible for multi-user deployments relying on namespace-based tenant isolation. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118760 attacked?: It is attacked over the network.
Am I affected by CVE-2026-118760?: Check whether you run 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

Fixed in: 2.17.0

Restrict network access to the Kubeflow Pipelines frontend to authorized users only. The fix is available in version 2.17.0; upgrade as soon as possible for multi-user deployments relying on namespace-based tenant isolation.

Technical details

The vulnerability is an authorization bypass in the frontend artifact routes (CWE-639: Authorization Bypass). The routes checked authentication but not authorization—verifying the caller's identity but not whether they had permission to access the requested namespace. An attacker who can reach the frontend and knows an artifact location can omit the namespace parameter or specify another tenant's namespace to access artifact contents, but cannot obtain arbitrary Kubernetes Secrets, modify storage, or execute code. The fix (version 2.17.0) implements namespace authorization validation middleware that performs SubjectAccessReview checks before allowing artifact access.

Affected products

Kubeflow Pipelines 0.5.1 to 2.16.x

Timeline

2026-10-29: disclosed
2026-04-08: patched: Fix commit merged

References

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