CVE-2026-77596 json
Kubeflow Pipelines API server lacks authorization for shared pipeline uploads
published 6d ago modified yesterday also EUVD-2026-117830 , GHSA-rjr3-43j3-4q8g
- cvss
- 9.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/kubeflow/pipelines 0.0.0-20260909234119-62516d8c525f
- kubeflow pipelines 2.18.0
Is CVE-2026-77596 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- yesterday
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/kubeflow/pipelines/security/advisories/GHSA-rjr3-43j3-4q8g referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/kubeflow/pipelines | <0.0.0-20260909234119-62516d8c525f |
0.0.0-20260909234119-62516d8c525f |
Affected products
- kubeflow pipelines
Classification
References
-
github.com
/kubeflow/pipelines/pull/14352
web
-
github.com
/kubeflow/pipelines/commit/62516d8c525f146b754cb515cf441dd0290ad841
web
-
github.com
/kubeflow/pipelines/security/advisories/GHSA-rjr3-43j3-4q8g
exploit, web
-
github.com
/kubeflow/pipelines/releases/tag/2.18.0
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-77596
advisory
-
github.com
/kubeflow/pipelines
package
Sources
- CVE List CVE-2026-77596
- GitHub Advisory GHSA-rjr3-43j3-4q8g
- NVD CVE-2026-77596
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.