Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Kubeflow Pipelines: Reflected XSS in the frontend pod information and events error responses

CVSS 3.1 6.1 MEDIUMEUVD CVSS 3.1 6.1 CVSS 3.1 · [email protected] · Secondary 6.1 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/kubeflow/pipelines 0.0.0-20251010122814-fedc25e3f725KEV status unknown

cve-program · CVE-2026-88986

Published

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.15.0, the frontend routes /pipeline/k8s/pod and /pipeline/k8s/pod/events use frontend/server/k8s-helper.ts to include untrusted podname and podnamespace query values and backend error details in HTML-capable error responses. An unauthenticated attacker can craft a link that executes JavaScript in the frontend origin when a user who satisfies the deployment's authentication and route-access requirements follows it and reaches an affected response. Cookie disclosure depends on cookie attributes, and server-side code execution or availability impact is not established. This issue is fixed in version 2.15.0.

Read the publisher's advisory

euvd · EUVD-2026-117825

Published

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.15.0, the frontend routes /pipeline/k8s/pod and /pipeline/k8s/pod/events use frontend/server/k8s-helper.ts to include untrusted podname and podnamespace query values and backend error details in HTML-capable error responses. An unauthenticated attacker can craft a link that executes JavaScript in the frontend origin when a user who satisfies the deployment's authentication and route-access requirements follows it and reaches an affected response. Cookie disclosure depends on cookie attributes, and server-side code execution or availability impact is not established. This issue is fixed in version 2.15.0.

Read the publisher's advisory

nvd · CVE-2026-88986

Published

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.15.0, the frontend routes /pipeline/k8s/pod and /pipeline/k8s/pod/events use frontend/server/k8s-helper.ts to include untrusted podname and podnamespace query values and backend error details in HTML-capable error responses. An unauthenticated attacker can craft a link that executes JavaScript in the frontend origin when a user who satisfies the deployment's authentication and route-access requirements follows it and reaches an affected response. Cookie disclosure depends on cookie attributes, and server-side code execution or availability impact is not established. This issue is fixed in version 2.15.0.

Read the publisher's advisory

osv · GHSA-g3qx-frcg-j979

Published

## Summary The Kubeflow Pipelines frontend reflected untrusted pod names and namespaces into HTML error responses from the pod-information and pod-events routes. An attacker could craft a link that causes JavaScript to execute in the frontend's origin when a user follows it and reaches an affected error response. Affected routes include `/pipeline/k8s/pod` and `/pipeline/k8s/pod/events` (the deployment's configured base path may differ). ## Impact and prerequisites Successful exploitation requires a victim to open an attacker-supplied link and reach the vulnerable response. JavaScript execution may expose information accessible to the victim's browser or perform actions in the application's origin. The attacker does not need an account merely to construct and deliver the link. The victim must satisfy the deployment's authentication and route-access requirements. Cookie theft depends on cookie attributes and deployment protections; it is not guaranteed. The submitted evidence does not establish an availability impact or server-side code execution. ## Technical details The pod handlers pass `podname` and `podnamespace` query values to `getPod` and `listPodEvents` in `frontend/server/k8s-helper.ts`. Before remediation, failure messages incorporated those values, along with backend error details, and were returned as HTML-capable string responses. Kubernetes rejecting an invalid resource name did not prevent the issue: the rejected name could still be included in the frontend's error response. [PR #12295](https://github.com/kubeflow/pipelines/pull/12295) changed the error construction to validate pod names and namespaces with `isAllowedResourceName`. Invalid values produce a constant error message instead of reflecting the supplied value, and backend error details are no longer included in these responses. The change includes invalid-resource-name tests. ## Affected versions and remediation Affected product: the Kubeflow Pipelines frontend server, identified as `ghcr.io/kubeflow/kfp-frontend`. Historical releases may use earlier image registry names. Upgrade to **KFP 2.15.0 or later**. The fix merged on October 10, 2025, in commit [fedc25e3f7251933d4a37b964bc3e8176beea28e](https://github.com/kubeflow/pipelines/commit/fedc25e3f7251933d4a37b964bc3e8176beea28e). It is first present in the **2.15.0** release, published November 25, 2025. The affected range is recorded as `< 2.15.0`. The original introduction version and separate maintenance-branch backports have not been established. These are KFP component versions, not Kubeflow platform or Python SDK versions. ## Distinction from existing artifact XSS [CVE-2023-6571](https://github.com/advisories/GHSA-7rvc-xw75-43jf), tracked in the repository as [GHSA-j9xw-rrjg-2p9r](https://github.com/kubeflow/pipelines/security/advisories/GHSA-j9xw-rrjg-2p9r), documents reflection of the artifact `source` parameter in an unknown-storage-source error. This report concerns different handlers and error construction: pod information and pod events. The artifact-source fix in [PR #9844](https://github.com/kubeflow/pipelines/pull/9844), released in 2.0.2, did not repair these pod responses. They required the later change in #12295. This independently fixable pod-route defect is tracked as CVE-2026-88986. It does not broaden CVE-2023-6571 or absorb artifact-content rendering and other XSS reports. ## Attribution **@pwny0** submitted this report on September 23, 2023, and retains the reporter credit. **@JerT33** authored the remediation in PR #12295. Fix attribution is separate from vulnerability-report attribution.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-88986 · CVE overview and exploitation status

EUVD-2026-117825

GHSA-g3qx-frcg-j979

cve-program · CVE-2026-88986

euvd · EUVD-2026-117825

nvd · CVE-2026-88986

osv · GHSA-g3qx-frcg-j979

Related changes

Linked by CVE identifier
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 10:01 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current