Is CVE-2026-118758 exploited in the wild?

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

How severe is CVE-2026-118758?

High severity, with a CVSS score of 7.5, published 29 October 2026.

Which products and versions are affected?

Kubeflow Pipelines prior to 2.18.0.

Is there a fix for CVE-2026-118758?

Yes: fixed in 2.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-118758 attacked?

It is attacked over the network.

Am I affected by CVE-2026-118758?

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-118758: Kubeflow Pipelines path traversal in artifact handler

CVE-2026-118758 · Severity: high · CVSS 7.5 · Published 2026-10-29

Kubeflow Pipelines is an open-source system for building and managing machine learning workflows. A path-traversal vulnerability in the artifact-serving component allows an attacker with access to the GET /artifacts/get API endpoint to read files outside the intended volume by supplying specially crafted file paths, potentially exposing sensitive data stored on the system.

Technologies: Kubeflow Pipelines. Vendors: Kubeflow.

Quick answers

Is CVE-2026-118758 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118758 being exploited in the wild.
How severe is CVE-2026-118758?: High severity, with a CVSS score of 7.5, published 29 October 2026.
Which products and versions are affected?: Kubeflow Pipelines prior to 2.18.0.
Is there a fix for CVE-2026-118758?: Yes: fixed in 2.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118758 attacked?: It is attacked over the network.
Am I affected by CVE-2026-118758?: 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.18.0

Technical details

The volume artifact handler for GET /artifacts/get?source=volume prior to 2.18.0 does not properly validate and confine caller-supplied file paths to the selected volume, enabling path traversal attacks. The vulnerability affects both the frontend pod (when artifact proxying is disabled) and the artifact-service pod in the selected namespace (when proxying is enabled). Exploitation requires network access to the route and knowledge of an existing mounted volume; deployments with authentication disabled need no credentials, while multi-user deployments require namespace authorization.

Affected products

Kubeflow Pipelines prior to 2.18.0

Timeline

2026-10-29: disclosed

References

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