CVE-2026-54745

Kubeflow Pipelines: Unauthenticated SSRF and HTTP smuggling in Kubeflow Pipelines frontend /_proxy/ route, bypasses ENABLE_AUTHZ=true

Published Aug 28, 2026 CVSS 3.1 · 10 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Prior to 2.17.0, Kubeflow Pipelines frontend exposes an unauthenticated Server‑Side Request Forgery via the /_proxy/ route. The /_proxy/ handler accepts any HTTP or HTTPS target, forwards all request headers—including Authorization, Cookie, and X‑Forwarded‑For—without a host allowlist, allowing an attacker to reach loopback, RFC1918, or cluster‑local addresses. If ENABLE_AUTHZ=true, the route remains outside the authorization middleware, so anyone with access to the UI can read or modify internal services, potentially exposing cloud metadata credentials, Kubernetes APIs, or other cluster‑internal endpoints.

Affected Systems

Kubeflow Pipelines is the vendor and product; all frontend deployments running Kubeflow Pipelines versions prior to 2.17.0 are vulnerable. The unprotected routes include /apis/v1beta1/_proxy/, /apis/v2beta1/_proxy/, /pipeline/apis/v1beta1/_proxy/, and /pipeline/apis/v2beta1/_proxy/, and the issue can also be triggered via a crafted Referer header. No specific minor releases are listed beyond the major 2.17.0 fix, so any earlier build must be considered at risk.

Risk and Exploitability

With a CVSS score of 10, this flaw represents a high‑severity, remote exploitation vector that does not require authentication. The EPSS score is not available, but the flaw is not yet listed in CISA KEV, indicating no publicly known exploits yet. Nevertheless, because the route is reachable by any user of the Pipelines UI and allows arbitrary outbound traffic, the likelihood of misuse is high, especially in shared or multi‑tenant clusters where internal services are valuable targets.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Kubeflow Pipelines 2.17.0 or later to receive the patch that removes the unauthenticated /_proxy/ route and enforces a host allowlist.
  • If an upgrade is not immediately possible, restrict access to the /_proxy/ endpoints by network policies, firewall rules, or by disabling the ENABLE_AUTHZ=true configuration so that the route is not exposed.
  • As a temporary workaround, modify the server/proxy-middleware to implement a host allowlist or to block loopback, RFC1918, and cluster‑local addresses before forwarding requests, ensuring that only externally reachable services can be contacted.

Generated by OpenCVE AI on August 28, 2026 at 21:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Kubeflow
Kubeflow pipelines
Vendors & Products Kubeflow
Kubeflow pipelines
Type Values Removed Values Added
Description 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.
Title Kubeflow Pipelines: Unauthenticated SSRF and HTTP smuggling in Kubeflow Pipelines frontend /_proxy/ route, bypasses ENABLE_AUTHZ=true
Weaknesses CWE-284
CWE-918
References
Metrics cvssV3_1

{'score': 10, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-284

    Improper Access Control

  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 31, 2026, 7:10 PM
Reserved
Jun 15, 2026, 11:12 PM
Status
Deferred
Published
Aug 28, 2026, 8:18 PM
Modified
Sep 9, 2026, 9:09 PM
Severity
Important
Public date
Aug 28, 2026, 3:59 PM