GPU VulnDB

Database/Container, Kubernetes & orchestration

OpenChoreo: WorkflowRun PUT authorizes on body labels, letting one project rewrite another's run ownership

CVSS 7.4CVE-2026-113727Container, Kubernetes & orchestrationcurated

Impact

The PUT .../workflowruns/{runName} route selects the stored WorkflowRun by the URL path but authorizes the request using the openchoreo.dev/project and openchoreo.dev/component labels submitted in the body. A caller who holds workflowrun:update for any one project or component in the namespace can name someone else's run in the path, submit ownership labels for a scope they do control, and rewrite the victim run's ownership. Every later authorization decision then treats them as the owner: they can read that run's build logs and Kubernetes events, delete it, modify pending spec.workflow.parameters, or wedge it permanently into ComponentValidationFailed. On a shared build platform in front of a GPU fleet that means one team reading another team's build output and tampering with the parameters of a pending build - build logs routinely carry tokens and internal endpoints. The advisory is explicit about the limits: the namespace comes from the URL, so this is cross-project and cross-component inside a single namespace, not anonymous and not cross-tenant across namespaces.

Who can reach it

An authenticated OpenChoreo caller holding workflowrun:update on at least one project or component in the same namespace as the victim run. Not reachable anonymously, and not usable across namespaces.

What to do

Upgrade to 1.0.6, 1.1.7 or 1.2.5 depending on your branch and restart the OpenChoreo API/controller - a control-plane daemon restart, no node disruption and no GPU workload impact. Until then, narrowing workflowrun:update so that a namespace holds only one trust domain removes the cross-project path.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-113727https://github.com/openchoreo/openchoreo/pull/4596https://github.com/openchoreo/openchoreo/commit/0e311468bb704b0dce7753b89c9d0204009285ca

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.