CVE-2026-113727 json
OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs
published 2026-10-20 19 d ago modified 2026-11-05 3 d ago also GHSA-46r4-q7wv-32fc , GO-2026-6825 , EUVD-2026-105772
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
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.
Patch / fix
- go github.com/openchoreo/openchoreo 1.0.6, 1.1.7, 1.2.5
- github.com/openchoreo/openchoreo@0e31146 commit
- github.com/openchoreo/openchoreo@477031c commit
- github.com/openchoreo/openchoreo@91e1e86 commit
- github.com/openchoreo/openchoreo@d5ed0ef commit
- github.com/openchoreo/openchoreo#4596 pull request
- github.com/openchoreo/openchoreo#4618 pull request
- github.com/openchoreo/openchoreo#4626 pull request
- github.com/openchoreo/openchoreo#4627 pull request
- github.com/openchoreo/openchoreo/releases/tag/v1.0.6 release
- github.com/openchoreo/openchoreo/releases/tag/v1.1.7 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 17 d ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/openchoreo/openchoreo | >=1.0.0, <1.0.6 >=1.1.0, <1.1.7 >=1.2.0, <1.2.5 |
1.0.6 1.1.7 1.2.5 |
Affected products
- openchoreo openchoreo
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/openchoreo/openchoreo/pull/4596
web, patch
-
github.com
/openchoreo/openchoreo/pull/4618
web, patch
-
github.com
/openchoreo/openchoreo/pull/4626
web, patch
-
github.com
/openchoreo/openchoreo/pull/4627
web, patch
-
github.com
/openchoreo/openchoreo/commit/0e311468bb704b0dce7753b89c9d0204009285ca
web, patch
-
github.com
/openchoreo/openchoreo/commit/477031c6fece0666f144942fb02c0b579dacc0bb
web, patch
-
github.com
/openchoreo/openchoreo/commit/91e1e868eb8e0e67274109018d00a767b22eda14
web, patch
-
github.com
/openchoreo/openchoreo/commit/d5ed0ef62d9c9af7b05a72aed2bcbc0ac9d45426
web, patch
-
github.com
/openchoreo/openchoreo/security/advisories/GHSA-46r4-q7wv-32fc
web, advisory
-
github.com
/openchoreo/openchoreo/releases/tag/v1.0.6
web
-
github.com
/openchoreo/openchoreo/releases/tag/v1.1.7
web
-
github.com
/openchoreo/openchoreo/releases/tag/v1.2.5
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-113727
advisory
-
github.com
/openchoreo/openchoreo
package
Sources
- CVE List CVE-2026-113727
- GitHub Advisory GHSA-46r4-q7wv-32fc
- NVD CVE-2026-113727
- OSV GO-2026-6825
Fencer Vulns 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.