Details
This automatic path requires an enabled, unpinned recurring run consuming the targeted shared pipeline and an uploaded specification compatible with the run's inputs. Latest-version selection queries the newest ready pipeline version; it does not depend on the UpdatePipelineVersionByDefault setting.
The automatic execution path was verified by source inspection, including the 2.17.2 tag: recurring-run creation preserves an unpinned pipeline reference, the scheduled-workflow controller submits it to CreateRun, and the API resolves the latest version before constructing the workflow. This is distinct from the live upload-bypass reproduction above; an end-to-end scheduled victim-execution reproduction has not been performed as part of this maintainer assessment.
Execution occurs with the victim workload's permissions and access to its mounted data and credentials. It can compromise confidential data and execution integrity available to that workload. It does not inherently grant access to every secret in the victim namespace or cluster-admin privileges.
CVSS rationale
The retained CVSS v3.1 vector is 9.6 Critical — `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`.
- AV:N / AC:L / PR:L: an authenticated low-privilege tenant can submit a normal multipart version upload targeting a shared pipeline, without shared-pipeline write permission.
- UI:N: an existing unpinned recurring run can consume the injected version automatically; no further victim action is required.
- S:C: the scored consequence extends from unauthorized modification of the shared pipeline catalog to code execution under a separate victim workload's Kubernetes namespace and service-account authority, not merely modification of another catalog entry.
- C:H / I:H: attacker-controlled workload code can compromise the confidentiality and integrity of resources available under that victim execution authority. These impacts do not imply cluster-wide access.
- A:N: this vector does not claim an independently established availability impact.
Patches / Remediation
The fix merged into master on September 9, 2026 in kubeflow/pipelines#14352, commit 62516d8c525f146b754cb515cf441dd0290ad841.
The upload authorization helper now uses ResourceManager.IsEmptyNamespace to recognize both the empty string and the legacy model.NoNamespace ("-") representation of shared pipelines. It checks shared writes against the configured KFP system namespace through IsAuthorized, requiring create on the pipelines resource in the pipelines.kubeflow.org API group. This matches the gRPC shared-write policy without changing the stored pipeline namespace. Namespaced authorization, single-user behavior, and intentional latest-version scheduling remain unchanged.
The original fix by Vito Carolillo (@vcrll) was carried forward with its authorship and DCO sign-off preserved. Separate maintainer commits added regression coverage, sentinel handling, and test-harness compatibility corrections.
Validation
- 32 endpoint regression cases cover both v1beta1 and v2beta1 pipeline and pipeline-version uploads: allowed and denied shared writes (empty and sentinel namespaces), namespaced writes, and single-user behavior. Tests verify exact SubjectAccessReview attributes and preservation of stored namespaces.
- A negative control restoring the original early return caused the new shared-upload tests to fail, including denied requests returning HTTP 200 without an authorization check.
- The full server unit-test package and changed-package lint passed during remediation.
- E2E test clients were corrected to send their generated authentication token and target the tenant namespace for HTTP uploads. Kubernetes-native clients retain their constructor-configured namespace rather than receiving an unsupported upload parameter. Helper regression tests and E2E/API package compilation passed.
Release status and upgrade guidance
The first fixed release is [2.18.0](https://github.com/kubeflow/pipelines/releases/tag/2.18.0). Releases through 2.17.3 remain affected; the affected-version upper bound is <= 2.17.3 and the patched version is 2.18.0.
The 2.18 RBAC and client migration guide is included through PR #14655. Related trusted-scheduling changes do not replace upload authorization or remove previously uploaded versions. Roll out the matching server/manifests and review existing shared versions and schedules.
In multi-user deployments, callers that previously relied on unauthenticated or unauthorized shared uploads will now be rejected:
- UI: choose Private (the default in the upload dialog) for tenant-owned pipelines. Shared uploads require an authorized shared-pipeline writer.
- Python SDK: explicitly pass the tenant namespace, for example
client.upload_pipeline("pipeline.yaml", namespace="my-namespace"). SettingClient(namespace=...)alone does not populate this upload argument. - New versions: inherit the existing pipeline's namespace. Existing shared pipelines must be maintained by an identity with the required system-namespace pipeline permission, or re-uploaded as new namespaced pipelines with consuming runs and schedules repointed.
- Kubernetes-native uploads: retain their existing client-configured namespace contract.
Do not grant blanket system-namespace access or restore the authorization bypass to preserve old upload scripts. Grant only the required pipeline-write permission to designated shared-pipeline maintainers.
As an interim hardening measure before deploying the fix, operators can set REQUIRE_NAMESPACE_FOR_PIPELINES=true to reject empty-namespace pipeline operations, with the corresponding compatibility impact on shared uploads.
Restoring upload authorization does not remove previously uploaded malicious versions or migrate existing pipelines and runs. Operators should review shared-pipeline versions and consuming recurring runs for unauthorized changes; pinning to a reviewed version prevents subsequent latest-version substitution.
The visualization authorization issue is tracked separately in GHSA-w9j6-6675-75m4 and is outside this fix's scope.
Resources
backend/src/apiserver/server/pipeline_upload_server.go:387-421(canUploadVersionedPipeline; bypass at:401-403),:118-138,:290-312backend/src/apiserver/server/pipeline_server.go:1290-1306(canAccessPipeline; load-bearing comment:1290-1292)backend/src/apiserver/validation/namespace.go:25-30backend/src/apiserver/common/config.go:41,:73-74backend/src/apiserver/resource/resource_manager.go(CreateJob,fetchPipelineVersionFromPipelineSpec,CreateRun)backend/src/crd/controller/scheduledworkflow/controller.go(submitNewWorkflowIfNotAlreadySubmitted)backend/src/apiserver/storage/pipeline_store.go(GetLatestPipelineVersion)- Distinct from CVE-2023-6570 and CVE-2023-6571 (both in
kubeflow/kubeflow, different components and classes).