CVE-2026-118759

Kubeflow Pipelines: Run log streaming endpoint bypasses namespace authorization, exposing pod execution logs cross-tenant

Published Oct 29, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the API server's GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler retrieved logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and suitable pod or node identifier can read live or archived logs with the API server's permissions. For live logs, the caller-controlled node ID was also accepted as a pod name without verifying that the pod belonged to the requested run, allowing a known run ID to select the namespace of an unrelated pod and read its main container logs. The handler does not authenticate requests itself, although an external authentication gate or network policy can limit reachability. Exposed logs can contain sensitive workload data or credentials. This issue is fixed in version 2.18.0.

Analysis

AI-generated

Technical impact

The vulnerability in Kubeflow Pipelines allows a caller who can reach the API server and knows a victim run ID and node identifier to retrieve logs from that run without any authorization checks. The GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler does not verify that the node belongs to the requested run, so an attacker can read live or archived logs from a pod in an unrelated namespace. These logs may contain private data or credentials, resulting in a confidentiality breach.

Affected Systems

Kubeflow Pipelines prior to version 2.18.0 is affected. Users running any earlier version of the Kubeflow Pipelines component should review the release notes and upgrade to 2.18.0 or later to remediate the issue.

Risk and Exploitability

The CVSS score of 7.5 indicates medium to high severity. The EPSS score of < 1% (0.00336) indicates a low probability of exploitation. The vulnerability is not listed in the KEV catalog, suggesting no widespread known exploits. The likely attack vector requires network reachability to the API server or an authenticated session, which an attacker can obtain through an externally exposed backend or insufficient network segmentation. Once accessed, the attacker can read logs across tenant boundaries without additional permissions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kubeflow Pipelines to version 2.18.0 or later to remove the unauthorized log access flaw
  • Ensure that the API server is protected by authentication and appropriate role‑based access controls so that only authorized users can query run logs
  • If upgrading immediately is not feasible, limit network access to the API server and apply network policies or external authentication gateways to prevent unauthorized reachability

Generated by OpenCVE AI on November 2, 2026 at 13:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-wg5q-x4j9-qm54 Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Kubeflow
Kubeflow pipelines
Vendors & Products Kubeflow
Kubeflow pipelines
Type Values Removed Values Added
Description Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the API server's GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler retrieved logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and suitable pod or node identifier can read live or archived logs with the API server's permissions. For live logs, the caller-controlled node ID was also accepted as a pod name without verifying that the pod belonged to the requested run, allowing a known run ID to select the namespace of an unrelated pod and read its main container logs. The handler does not authenticate requests itself, although an external authentication gate or network policy can limit reachability. Exposed logs can contain sensitive workload data or credentials. This issue is fixed in version 2.18.0.
Title Kubeflow Pipelines: Run log streaming endpoint bypasses namespace authorization, exposing pod execution logs cross-tenant
Weaknesses CWE-200
CWE-862
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 5:13 PM
Reserved
Oct 28, 2026, 7:20 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 5:18 PM
Modified
Oct 30, 2026, 6:17 PM
Severity
Important
Public date
Oct 29, 2026, 4:30 PM