Improper Access Control Affecting kubeflow-pipelines-frontend package, versions <2.17.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-KUBEFLOWPIPELINESFRONTEND-19504486
- published3 Sept 2026
- disclosed28 Aug 2026
Introduced: 28 Aug 2026
CVE-2026-54745 (opens in a new tab)How to fix?
Upgrade Minimos:latest kubeflow-pipelines-frontend to version 2.17.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kubeflow-pipelines-frontend package and not the kubeflow-pipelines-frontend package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.17.0, the Kubeflow Pipelines frontend exposes an unauthenticated server-side request forgery vulnerability through the /_proxy/ route in frontend/server/proxy-middleware.ts. The _routePathWithReferer() function accepts an arbitrary attacker-controlled HTTP or HTTPS target and passes its origin to createProxyMiddleware without a host allowlist or filtering for loopback, link-local, RFC1918, or cluster-local addresses. The route remains outside the authorization middleware when ENABLE_AUTHZ=true and is reachable through /apis/v1beta1/_proxy/, /apis/v2beta1/_proxy/, /pipeline/apis/v1beta1/_proxy/, and /pipeline/apis/v2beta1/_proxy/, including through a crafted Referer header. Requests can forward attacker-controlled methods, headers such as Authorization, Cookie, and X-Forwarded-For, and POST bodies to reachable internal services, while returning the upstream response to the unauthenticated client. This can expose cloud metadata credentials, Kubernetes or service APIs, and other cluster-internal endpoints to unauthorized read or modification. This issue is fixed in version 2.17.0.
References
- https://www.cve.org/CVERecord?id=CVE-2026-54745
- https://osv.dev/vulnerability/MINI-2wq8-ch9c-ffp4
- https://osv.dev/vulnerability/CVE-2026-54745
- https://github.com/kubeflow/pipelines/commit/a35f97aa4c17b25572369e5022546ab4421bdbdd
- https://github.com/kubeflow/pipelines/pull/13511
- https://github.com/kubeflow/pipelines/releases/tag/2.17.0
- https://github.com/kubeflow/pipelines/security/advisories/GHSA-gqww-5pj5-8fq7