Critical (9.6) in kubeflow pipelines. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/kubeflow/pipelines 0.0.0-20260909234119-62516d8c525f.
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the multi-user HTTP endpoints POST /apis/v2beta1/pipelines/upload and POST /apis/v2beta1/pipelines/upload_version call canUploadVersionedPipeline, which returns without SubjectAccessReview when the target namespace is empty while REQUIRE_NAMESPACE_FOR_PIPELINES defaults to false. A low-privilege tenant can create shared pipelines or inject attacker-controlled versions into existing shared pipelines without the required write permission; if the API server is directly reachable without an authenticating proxy, an unauthenticated caller can exploit the same bypass, while deployments protected by such a proxy do not expose anonymous access. An enabled unpinned recurring run that follows the latest version can then execute the injected specification in another tenant's namespace under that workload's service account, while pinned or embedded-specification runs are not automatically substituted. This issue is fixed in version 2.18.0.
Severity
CVSS 3.1
9.6 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-639Authorization Bypass Through User-Controlled Key CWE-862Missing Authorization
Show the promptExplain CVE-2026-77596 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77596?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77596?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77596 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.