# CVE-2026-113727: OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-46r4-q7wv-32fc

## What is CVE-2026-113727?

CVE-2026-113727 is a high-severity vulnerability in openchoreo, published on 20 Oct 2026. 

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-113727?

6 open source packages ship an affected version, including github.com/openchoreo/openchoreo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openchoreo/openchoreo` | Go | From 1.0.0 | 1.0.6 |
| `github.com/openchoreo/openchoreo` | Go | From 1.0.0 | 1.0.6 |
| `github.com/openchoreo/openchoreo` | Go | From 1.1.0 | 1.1.7 |
| `github.com/openchoreo/openchoreo` | Go | From 1.1.0 | 1.1.7 |
| `github.com/openchoreo/openchoreo` | Go | From 1.2.0 | 1.2.5 |
| `github.com/openchoreo/openchoreo` | Go | From 1.2.0 | 1.2.5 |

## How do I fix CVE-2026-113727?

Upgrade github.com/openchoreo/openchoreo to a fixed version for your release line: 1.0.6, 1.1.7 or 1.2.5.

## Is CVE-2026-113727 being exploited?

There is no known exploitation of CVE-2026-113727 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113727 and fix it if it is affected.

What it is: CVE-2026-113727 is a high-severity vulnerability in openchoreo, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113727 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openchoreo/openchoreo (Go): affected from 1.0.0; fixed in 1.0.6
- github.com/openchoreo/openchoreo (Go): affected from 1.0.0; fixed in 1.0.6
- github.com/openchoreo/openchoreo (Go): affected from 1.1.0; fixed in 1.1.7
- github.com/openchoreo/openchoreo (Go): affected from 1.1.0; fixed in 1.1.7
- github.com/openchoreo/openchoreo (Go): affected from 1.2.0; fixed in 1.2.5
- github.com/openchoreo/openchoreo (Go): affected from 1.2.0; fixed in 1.2.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113727/ (Markdown: https://insights.sbomify.com/CVE-2026-113727/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113727
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113727
- OSV: https://osv.dev/vulnerability/CVE-2026-113727

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113727/
Summaries are generated and may contain mistakes; the official description above is the record.