Approved changes feed: RSS · Atom
cpe:2.3:a:kubeflow:pipelines:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Kubeflow (77ae1be4-7ba0-5fe9-a078-f8b5b06cfb80) |
|---|---|
| Product | Pipelines (6f020ab9-f4f1-54db-862b-45837801f531) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/kubeflow/pipelines |
purl2cpe | 2026-06-01 10:15:30.031369 |
pkg:golang/github.com/kubeflow/pipelines |
purl2cpe | 2026-06-01 10:15:30.031371 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-118760 |
vulnerable | 2026-11-03 10:17:04.379415 |
Kubeflow Pipelines: Missing namespace authorization permits cross-tenant artifact reads
MEDIUM (6.5)
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. From 0.5.1 until 2.17.0, the frontend artifact routes did not check whether an authenticated user was authorized to access the requested namespace. A user who can reach the frontend and knows an artifact location can select another tenant's namespace, or omit the namespace and reach an unguarded direct handler, to read artifact contents such as datasets, models, or pipeline outputs. The issue applies to multi-user deployments that rely on Kubeflow Pipelines authorization for tenant isolation. Authentication at ingress identifies the caller but does not authorize access to the selected artifact namespace. The issue does not establish arbitrary Kubernetes Secret disclosure, storage modification, or server-side code execution. This issue is fixed in version 2.17.0.
Published: 2026-10-29T16:35:05.192Z
Updated: 2026-11-03T16:03:50.453Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-118759 |
vulnerable | 2026-11-03 10:17:04.307028 |
Kubeflow Pipelines: Run log streaming endpoint bypasses namespace authorization, exposing pod execution logs cross-tenant
HIGH (7.5)
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the API server's GET /apis/v1alpha1/runs/{run_id}/nodes/{node_id}/log handler retrieved logs without authorizing the caller against the selected run. A caller who can reach the backend and knows a victim run ID and suitable pod or node identifier can read live or archived logs with the API server's permissions. For live logs, the caller-controlled node ID was also accepted as a pod name without verifying that the pod belonged to the requested run, allowing a known run ID to select the namespace of an unrelated pod and read its main container logs. The handler does not authenticate requests itself, although an external authentication gate or network policy can limit reachability. Exposed logs can contain sensitive workload data or credentials. This issue is fixed in version 2.18.0.
Published: 2026-10-29T16:30:25.711Z
Updated: 2026-10-30T17:13:29.148Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-118758 |
vulnerable | 2026-11-03 10:17:04.256609 |
Kubeflow: Unauthenticated path traversal to arbitrary file read on ml-pipeline-ui via the volume artifact source
HIGH (7.5)
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the volume artifact handler for GET /artifacts/get?source=volume did not confine a caller-supplied file path to the selected volume. A caller who can reach the route and identify an existing mounted volume can use path traversal to read files outside that volume when the artifact-serving process can read them. The frontend pod serves the request when artifact proxying is disabled, while the selected namespace's artifact-service pod serves it when proxying is enabled. A deployment with authentication disabled requires no application credentials; in multi-user deployments, the caller ordinarily must be authorized for the supplied namespace. This issue is fixed in version 2.18.0.
Published: 2026-10-29T16:12:42.138Z
Updated: 2026-10-29T20:18:30.607Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-118761 |
vulnerable | 2026-11-03 10:17:04.218336 |
Kubeflow Pipelines: Pipeline archive upload allows decompression bomb to exhaust server memory
HIGH (7.5)
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the API server decompressed uploaded pipeline archives without adequately bounding expanded data while locating or reading the pipeline file. A small ZIP or gzip-compressed tar archive can consume disproportionately large memory and exhaust API-server resources. Multipart pipeline and pipeline-version upload processing performs decompression before namespace authorization, so a reachable caller does not need a successful pipeline-create authorization decision. URL-import handlers authorize before fetching and decompressing a remote archive. The amount of expansion required to interrupt service depends on deployment resource limits and concurrent activity, and no specific archive is guaranteed to crash every deployment. This issue is fixed in version 2.18.0.
Published: 2026-10-29T16:37:44.333Z
Updated: 2026-10-29T20:18:59.625Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9526 |
vulnerable | 2026-06-08 07:00:28.121385 |
Stored XSS in Kubeflow Pipeline View
There exists a stored XSS Vulnerability in Kubeflow Pipeline View web UI. The Kubeflow Web UI allows to create new pipelines. When creating a new pipeline, it is possible to add a description. The description field allows html tags, which are not filtered properly. Leading to a stored XSS. We recommend upgrading past commit 930c35f1c543998e60e8d648ce93185c9b5dbe8d
Published: 2024-11-18T13:30:21.818Z
Updated: 2024-11-21T10:24:31.751Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.