OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs

Summary

OpenChoreo is a developer platform for Kubernetes. From 1.0.0 until 1.0.6, 1.1.7, and 1.2.5, the PUT .../workflowruns/{runName} update route authorizes a request using the openchoreo.dev/project and openchoreo.dev/component labels in the submitted body while selecting the stored WorkflowRun by the URL path. An authenticated caller with workflowrun:update for one project or component in the same namespace can name another run in the path, submit ownership labels for a scope they control, and rewrite the victim run's ownership labels. Subsequent authorization then treats the attacker as authorized to read build logs and Kubernetes events, delete the run, modify pending spec.workflow.parameters, or place the run into a permanent ComponentValidationFailed state. The namespace comes from the URL, so the issue is cross-project or cross-component within one namespace and is not anonymously reachable or cross-tenant. This issue is fixed in 1.0.6, 1.1.7, and 1.2.5.

Timeline

1. Oct 20, 2026, 9:08 PM UTCCVE published
2. Oct 22, 2026, 9:34 PM UTCFirst seen by cve.now
3. Oct 23, 2026, 2:10 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

4. Oct 23, 2026, 2:10 AM UTCRecord last updated

Affected versions

• openchoreo openchoreo

  From 1.0.0 · fixed in 1.0.6; From 1.1.0 · fixed in 1.1.7; From 1.2.0 · fixed in 1.2.5

• github.com/openchoreo/openchoreoGo

  From 1.0.0 · fixed in 1.0.6

• github.com/openchoreo/openchoreoGo

  From 1.1.0 · fixed in 1.1.7

• github.com/openchoreo/openchoreoGo

  From 1.2.0 · fixed in 1.2.5

References 12