ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-118759

Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs

Published Oct 30, 2026 · catalog updated Oct 30, 2026 · Kubeflow Pipelines: Run-log endpoint

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-118759. EPSS is 0.34%. Act only if a listed version of Kubeflow Pipelines: Run-log endpoint is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Kubeflow Pipelines: Run-log endpoint).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.34%
Remediation
Version ranges on file
Affected products
Go github.com/kubeflow/pipelines · go github.com/kubeflow/pipelines · golang github.com

## Summary The Kubeflow Pipelines API server's handler retrieves logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and a suitable pod or node identifier can read live or archived logs using the API server's permissions. For live logs, the vulnerable handler also accepts the supplied node ID as a pod name in the run's namespace without verifying that the pod belongs to the run. Depending on the API server's pod-log permissions, a known run ID can therefore permit reading the container logs of an unrelated pod in that namespace. Logs may contain sensitive workload data or credentials. The affected handler does not authenticate the request itself. An external authentication gate or network policy can restrict reachability; public ingress exposure and unauthenticated enumeration of run IDs are not assumed. ## Remediation Upgrade the API server to **[Kubeflow Pipelines 2.18.0](https://github.com/kubeflow/pipelines/releases/tag/2.18.0)**. Versions through 2.17.3 are affected; the first affected release has not been established. [PR #13684](https://github.com/kubeflow/pipelines/pull/13684) authorizes the caller with the verb before retrieving live or archived logs. For live logs, it also verifies that the pod's label matches the requested run. Custom Kubernetes roles must grant on in the API group; the bundled viewer and editor roles include it. Shared read access alone does not grant log access. Until upgrading, restrict access to the backend log endpoint. Focused regression tests cover authorization denial, HTTP identity propagation, pod/run mismatch, archive retrieval, and cancellation; no new deployed-cluster end-to-end test was performed for this assessment. ## Credit [bugbunny.ai](https://bugbunny.ai) discovered and reported the issue. Nayyar ([@naruto-lgtm](https://github.com/naruto-lgtm)) authored the fix in #13684. [@patchmyday](https://github.com/patchmyday), [@thesecguy45](https://github.co

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/kubeflow/pipelines0 → 0.0.0-20260904182349-be4723e33727
  • Go github.com/kubeflow/pipelines1.7.0-alpha.3
  • go github.com/kubeflow/pipelines< 0.0.0-20260904182349-be4723e33727
  • go github.com/kubeflow/pipelines<0.0.0-20260904182349-be4723e33727||=1.7.0-alpha.3
  • go github.com/kubeflow/pipelines= 1.7.0-alpha.3
  • golang github.comversion unspecified

How to fix CVE-2026-118759

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-118759. EPSS is 0.34%. Act only if a listed version of Kubeflow Pipelines: Run-log endpoint is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.0.0-20260904182349-be4723e33727, 1.7.0-alpha.3, < 0.0.0-20260904182349-be4723e33727, <0.0.0-20260904182349-be4723e33727||=1.7.0-alpha.3, = 1.7.0-alpha.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information; CWE-862: Missing Authorization. EPSS 0.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 30, 2026 · GitHub Advisory Database

    Detected

    ## Summary The Kubeflow Pipelines API server's handler retrieves logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and a suitable pod or node identifier can read live or archived logs using the API server's permissions. For live logs, the vulnerable handler also accepts the supplied node ID as a pod name in the run's namespac

  2. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    github.com/kubeflow/pipelines fixed in 0.0.0-20260904182349-be4723e33727

  3. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    github.com/kubeflow/pipelines fixed in 0.0.0-20260904182349-be4723e33727

  4. Oct 30, 2026 · GitHub Advisory Database

    Updated

    ## Summary The Kubeflow Pipelines API server's handler retrieves logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and a suitable pod or node identifier can read live or archived logs using the API server's permissions. For live logs, the vulnerable handler also accepts the supplied node ID as a pod name in the run's namespac

Sources

  • CVE.orgVulnerability recordCVE-2026-118759

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-wg5q-x4j9-qm54

    Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-118759

    The Kubeflow Pipelines API server's GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler retrieves logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and a suitable pod or node identifier can read live or archived logs using the API server's permissions. For live logs, the vulnerable handler also accepts the supplied n

    advisories.gitlab.com
  • GitLab Advisory DatabasePackage advisorygo/github.com/kubeflow/pipelines/CVE-2026-118759.yml

    The Kubeflow Pipelines API server's + handler retrieves logs without authorizing the caller against the selected run. + A caller who can reach the backend and knows a victim run ID and a suitable pod + or node identifier can read live or archived logs using the API server's permissions.\n\nFor + live logs, the vulnerable handler also accepts the supplied node ID as a pod name + in the run's namesp

    gitlab.com
  • Go Vulnerability DatabasePackage advisoryGHSA-wg5q-x4j9-qm54

    Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs

    osv.dev
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-wg5q-x4j9-qm54

    Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs

    osv.dev

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseNov 7, 2026
  • Go Vulnerability DatabaseNov 5, 2026
  • GitLab Advisory DatabaseNov 3, 2026
  • OpenSSF OSV / OSV ScannerNov 2, 2026
  • GitLab Advisory DatabaseNov 1, 2026
  • CVE.orgOct 31, 2026