CVE-2026-113727
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 37% of all known CVEs.
References
Related Vulnerabilities
Other CWE-639 (Authorization Bypass Through User-Controlled Key) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-6875 | Critical | 9.8 | 90% | - | - |
| CVE-2024-46982 | High | 7.5 | 59% | - | Fix |
| CVE-2021-45428 | Critical | 9.8 | 57% | - | - |
| CVE-2019-17382 | Critical | 9.1 | 54% | - | Fix |
| CVE-2019-13360 | Critical | 9.8 | 24% | - | - |
| CVE-2023-48783 | Medium | 5.4 | 22% | - | Fix |
Common questions
How do I fix CVE-2026-113727?
No published fix for CVE-2026-113727 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-113727 being actively exploited?
Not that we know of. CVE-2026-113727 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.43% is the estimated probability that it will be exploited in the next 30 days. That is higher than 37% of all scored CVEs.
How severe is CVE-2026-113727?
CVE-2026-113727 has a CVSS v3 base score of 7.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-113727
Markdown
[](https://tridentstack.com/cve/CVE-2026-113727)HTML
<a href="https://tridentstack.com/cve/CVE-2026-113727"><img src="https://tridentstack.com/cve/badge/CVE-2026-113727.svg" alt="CVE-2026-113727"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-23.