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.

Affected: Go: github.com/kubeflow/pipelines

## 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 fro…