CVE-2026-113727: OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs
Summary The OpenChoreo API server authorized PUT .../workflowruns/{runName} against ownership metadata taken from the request body, while the object it actually mutated was selected by the URL path. Nothing forced the two to agree. A WorkflowRun's membership in a project and component is carried entirely by its openchoreo.dev/project and openchoreo.dev/component labels.
Published Oct 21, 2026
Affected packages
github.com/openchoreo/openchoreo
- Ecosystem
- Go
- Affected
- >= 1.0.0, < 1.0.6
- Fixed in
- 1.0.6
- Check
go list -m github.com/openchoreo/openchoreo
github.com/openchoreo/openchoreo
- Ecosystem
- Go
- Affected
- >= 1.1.0, < 1.1.7
- Fixed in
- 1.1.7
- Check
go list -m github.com/openchoreo/openchoreo
github.com/openchoreo/openchoreo
- Ecosystem
- Go
- Affected
- >= 1.2.0, < 1.2.5
- Fixed in
- 1.2.5
- Check
go list -m github.com/openchoreo/openchoreo
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The OpenChoreo API server authorized PUT .../workflowruns/{runName} against ownership metadata taken from the request body, while the object it actually mutated was selected by the URL path. Nothing forced the two to agree.
A WorkflowRun's membership in a project and component is carried entirely by its openchoreo.dev/project and openchoreo.dev/component labels. Because the workflowrun:update check read those labels from the submitted object rather than the stored one, a caller holding workflowrun:update on one component could name a run belonging to a different project or component in the URL, supply labels for the component they legitimately control, pass the check, and have the unrelated run rewritten with their own ownership labels.
The namespace is taken from the URL and feeds both the authorization check and the Kubernetes read, so it cannot diverge. This is cross-project and cross-component escalation inside a single namespace, not a cross-tenant issue.
Impact
Rewriting the ownership labels transfers authority over the run. Every other WorkflowRun check (view, logs, events, status, delete, list) derives its scope from the stored labels, so once the write lands the policy engine legitimately grants the attacker access to an object they never had rights to. They can then:
- Read the victim's build logs. These stream raw pod logs from the workflow plane and routinely carry source paths, registry destinations, and credentials a build step echoed by accident.
- Read the run's Kubernetes events.
- Delete the run.
So the primary impact is confidentiality and availability, not only integrity. On the integrity side, spec.workflow.parameters can be overwritten on a pending run, and manipulating the two ownership labels can either wedge the run in a permanent ComponentValidationFailed condition or downgrade it to a standalone run that skips component validation.
Exploitation requires an authenticated caller with an AuthzRoleBinding or ClusterAuthzRoleBinding granting workflowrun:update at project or component scope in the victim's namespace, plus knowledge of the target run's name. An anonymous caller cannot reach this.
Patches
The authorization check now loads the stored WorkflowRun and derives every ownership attribute from it instead of from the request body. Separately, the openchoreo.dev/project and openchoreo.dev/component labels are now immutable on update, so an authorized caller cannot hand their own run to another project either.
| Line | Affected | Fixed in | | 1.0.x | 1.0.0 through 1.0.5 | 1.0.6 | | 1.1.x | 1.1.0 through 1.1.6 | 1.1.7 | | 1.2.x | 1.2.0 through 1.2.4 | 1.2.5 |
Upgrade to the patched release on your line. No configuration change is needed after upgrading.
Workarounds
If you cannot upgrade immediately, restrict who holds workflowrun:update.
Audit your AuthzRole and ClusterAuthzRole definitions for that action and remove it from any role granted to principals you would not trust with write access to every workflow run in the namespace. Among the roles shipped with OpenChoreo, only the system role workload-publisher lists workflowrun:update explicitly, and admin holds it through its * wildcard. Custom roles in your own values file may also include it, so check those.
Treat any credential bound to workload-publisher as privileged. CI systems are the usual holder, and a leaked CI token is enough to run this.
Credited to Tike00.
References
- https://github.com/openchoreo/openchoreo/security/advisories/GHSA-46r4-q7wv-32fc
- https://nvd.nist.gov/vuln/detail/CVE-2026-113727
- https://github.com/openchoreo/openchoreo/pull/4596
- https://github.com/openchoreo/openchoreo/pull/4618
- https://github.com/openchoreo/openchoreo/pull/4626
- https://github.com/openchoreo/openchoreo/pull/4627
- https://github.com/openchoreo/openchoreo/commit/0e311468bb704b0dce7753b89c9d0204009285ca
- https://github.com/openchoreo/openchoreo/commit/477031c6fece0666f144942fb02c0b579dacc0bb
- https://github.com/openchoreo/openchoreo/commit/91e1e868eb8e0e67274109018d00a767b22eda14
- https://github.com/openchoreo/openchoreo/commit/d5ed0ef62d9c9af7b05a72aed2bcbc0ac9d45426
- https://github.com/openchoreo/openchoreo/releases/tag/v1.0.6
- https://github.com/openchoreo/openchoreo/releases/tag/v1.1.7
- https://github.com/openchoreo/openchoreo/releases/tag/v1.2.5
- https://github.com/advisories/GHSA-46r4-q7wv-32fc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-73842
OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation
critical9.0Sep 4, 2026CVE-2026-73667
OpenChoreo: Authenticated OS command injection via OpenChoreo Workflow Plane templates enables code execution in privileged pods
high8.8Sep 2, 2026CVE-2026-73840
OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass)
medium5.3Sep 2, 2026CVE-2026-73841
OpenChoreo: Cross-project command execution and wirelog view access via OpenChoreo openchoreo-api exec and wirelogs endpoints
high8.8Sep 2, 2026CVE-2026-73843
OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs
critical9.6Sep 2, 2026
