Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1amended

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

CVE-2026-88986GHSA-g3qx-frcg-j979

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/kubeflow/pipelines 0.0.0-20251010122814-fedc25e3f725), redeploy, then verify what is actually installed.

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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2026-88986: 0.28% estimated exploitation activity in the next 30 days; percentile 20.21 (FIRST EPSS, 2026-11-10). 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 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-g3qx-frcg-j979

  2. Revision 1 · created ·

    Published from ghsa record GHSA-g3qx-frcg-j979

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-88986

Advisory: Kubeflow Pipelines: Reflected XSS in the frontend pod information and events error responses
IDs: CVE-2026-88986, GHSA-g3qx-frcg-j979
Record: https://patchnext.com/advisories/cve-2026-88986 (revision 2, source checked 10 Nov 2026, 06:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/kubeflow/pipelines 0.0.0-20251010122814-fedc25e3f725. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kubeflow/pipelines: affected < 0.0.0-20251010122814-fedc25e3f725; fixed in 0.0.0-20251010122814-fedc25e3f725

## Suggested inspection (read-only)
- Go github.com/kubeflow/pipelines: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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-g3qx-frcg-j979 (GitHub-reviewed advisory GHSA-g3qx-frcg-j979 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20251010122814-fedc25e3f725)
- Verified: https://osv.dev/vulnerability/GHSA-g3qx-frcg-j979 (OSV record GHSA-g3qx-frcg-j979 lists affected ranges: Go github.com/kubeflow/pipelines >=0 <0.0.0-20251010122814-fedc25e3f725 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…