Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Kubeflow Pipelines through 2.17.3 returns run logs without checking the caller's access to the run. An attacker who can reach the backend and knows a run ID and a pod or node ID can read those logs, which may include logs from unrelated pods in the same namespace. Upgrade to 2.18.0, or restrict access to the backend log endpoint until then.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 27th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-wg5q-x4j9-qm54
- OSV: GHSA-wg5q-x4j9-qm54
- github.com/kubeflow/pipelines/security/advisories/GHSA-wg5q-x4j9-qm54
- nvd.nist.gov/vuln/detail/CVE-2026-118759
- github.com/kubeflow/pipelines/pull/13684
- github.com/kubeflow/pipelines/commit/be4723e33727c6dad71a95cba61e8f61562ab20f
- github.com/kubeflow/pipelines
- github.com/kubeflow/pipelines/releases/tag/2.18.0