CVE-2026-113727
OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs
- High 7.4
Description
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.
Key facts
- Published
- 20 Oct 2026
- Last changed
- 23 Oct 2026
- Assigned by
- GitHub_M
- EPSS
- 0.465% likely to be exploited in the next 30 days, higher than 40.849% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 7.4CVSS 3.1, Highfrom the CNA (GitHub_M)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| openchoreo | openchoreo |
|
Timeline
- 20 Oct 2026 Published
Weakness
References
- https://github.com/openchoreo/openchoreo/security/advisories/GHSA-46r4-q7wv-32fc
- 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