Openchoreo: Authorization Bypass Through User-Controlled Key (CVE-2026-113727)
Published Last modified Sources: CVE.org, OSV, Hersteller
What is affected, what to do
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.
Update github.com/openchoreo/openchoreo to version 1.0.6.
- Affected
- Openchoreo
gte 1.0.0, < 1.0.6..*
- Openchoreo
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.4
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
7.4
CVSS v3
Severity High on the scale from 0 to 10.
Source: CVE.org, OSV, Hersteller
0.5 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 40.1
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 79.82 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.4 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.4
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.5 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 40.1
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-639
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5, GitHub Security Advisories
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| openchoreo | openchoreo |
|
|
| go | github.com/openchoreo/openchoreo |
|
|
Vendors and products
Weakness classes (CWE)
CWE-639Authorization Bypass Through User-Controlled Key
Base
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Entry at MITRE CWE-639
References & sources
- github.comopenchoreo/openchoreo/commit/0e311468bb704b0dce7753b89c9d020400…x_refsource_MISC, web
- github.comopenchoreo/openchoreo/commit/477031c6fece0666f144942fb02c0b579d…x_refsource_MISC, web
- github.comopenchoreo/openchoreo/commit/91e1e868eb8e0e67274109018d00a767b2…x_refsource_MISC, web
- github.comopenchoreo/openchoreo/commit/d5ed0ef62d9c9af7b05a72aed2bcbc0ac9…x_refsource_MISC, web
- github.comopenchoreo/openchoreo/pull/4596x_refsource_MISC, web
- github.comopenchoreo/openchoreo/pull/4618x_refsource_MISC, web
- github.comopenchoreo/openchoreo/pull/4626x_refsource_MISC, web
- github.comopenchoreo/openchoreo/pull/4627x_refsource_MISC, web
- github.comopenchoreo/openchoreo/releases/tag/v1.0.6x_refsource_MISC, web
- github.comopenchoreo/openchoreo/releases/tag/v1.1.7x_refsource_MISC, web
- github.comopenchoreo/openchoreo/releases/tag/v1.2.5x_refsource_MISC, web
- github.comopenchoreo/openchoreo/security/advisories/GHSA-46r4-q7wv-32fcx_refsource_CONFIRM, web
- NVD (NIST)vuln/detail/CVE-2026-113727advisory
- github.comopenchoreo/openchoreopackage
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-113727","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-23T02:10:51.680790Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedGitHub
CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
Weakness type: CWE-639
Description added or changed
New references:- 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
and 8 more references
Show 16 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.CVSS added —AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:LWeakness type (CWE) added —CWE-639Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/113xxx/CVE-2026-113727.json">CVE-2026-113727</a>Reference added —https://github.com/openchoreo/openchoreo/commit/0e311468bb704b0dce7753b89c9d0204009285caReference added —https://github.com/openchoreo/openchoreo/commit/477031c6fece0666f144942fb02c0b579dacc0bbReference added —https://github.com/openchoreo/openchoreo/commit/91e1e868eb8e0e67274109018d00a767b22eda14Reference added —https://github.com/openchoreo/openchoreo/commit/d5ed0ef62d9c9af7b05a72aed2bcbc0ac9d45426Reference added —https://github.com/openchoreo/openchoreo/pull/4596Reference added —https://github.com/openchoreo/openchoreo/pull/4618Reference added —https://github.com/openchoreo/openchoreo/pull/4626Reference added —https://github.com/openchoreo/openchoreo/pull/4627Reference added —https://github.com/openchoreo/openchoreo/releases/tag/v1.0.6Reference added —https://github.com/openchoreo/openchoreo/releases/tag/v1.1.7Reference added —https://github.com/openchoreo/openchoreo/releases/tag/v1.2.5Reference added —https://github.com/openchoreo/openchoreo/security/advisories/GHSA-46r4-q7wv-32fcSource identifier: security-advisories@github.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-113727"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-113727.svg?lang=en" alt="CVE-2026-113727 – NEOSEC Intel" height="20"></a>