Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs
CVE-2026-118759GHSA-wg5q-x4j9-qm54
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/kubeflow/pipelines
- Affected
- < 0.0.0-20260904182349-be4723e33727>= 1.7.0-alpha.3, <= 1.7.0-alpha.3
- Fixed in
- 0.0.0-20260904182349-be4723e33727
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-wg5q-x4j9-qm54 lists affected ranges: Go github.com/kubeflow/pipelines >=0 =1.7.0-alpha.3 <=1.7.0-alpha.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-wg5q-x4j9-qm54 lists affected ranges: Go github.com/kubeflow/pipelines >=0 =1.7.0-alpha.3 <=1.7.0-alpha.3
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-118759: 0.34% estimated exploitation activity in the next 30 days; percentile 27.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary 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 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 `main` 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-wg5q-x4j9-qm54
- Revision 1 · created ·
Published from ghsa record GHSA-wg5q-x4j9-qm54
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-118759 Advisory: Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs IDs: CVE-2026-118759, GHSA-wg5q-x4j9-qm54 Record: https://patchnext.com/advisories/cve-2026-118759 (revision 2, source checked 31 Oct 2026, 06:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/kubeflow/pipelines 0.0.0-20260904182349-be4723e33727. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/kubeflow/pipelines: affected < 0.0.0-20260904182349-be4723e33727; >= 1.7.0-alpha.3, <= 1.7.0-alpha.3; fixed in 0.0.0-20260904182349-be4723e33727 ## Suggested inspection (read-only) - Go github.com/kubeflow/pipelines: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/kubeflow/pipelines. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-wg5q-x4j9-qm54 (GitHub-reviewed advisory GHSA-wg5q-x4j9-qm54 lists affected ranges: Go github.com/kubeflow/pipelines >=0 =1.7.0-alpha.3 <=1.7.0-alpha.3) - Verified: https://osv.dev/vulnerability/GHSA-wg5q-x4j9-qm54 (OSV record GHSA-wg5q-x4j9-qm54 lists affected ranges: Go github.com/kubeflow/pipelines >=0 =1.7.0-alpha.3 <=1.7.0-alpha.3) Commands are suggestions: review each one before running it.
Loading voting…