{"id":"CVE-2026-113727","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-113727","generatedAt":"2026-10-28T07:42:04.565Z","title":"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.","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.","published":"2026-10-20T22:19:30.000Z","lastModified":"2026-10-23T03:16:31.000Z","status":"Awaiting Analysis","sourceIdentifier":"security-advisories@github.com","cvss":{"version":"3.1","score":7.4,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L"},"cwe":["CWE-639"],"affected":[],"epss":{"score":0.00465,"percentile":0.40109,"date":"2026-10-27","history":[{"date":"2026-10-21","score":0.00434,"percentile":0.36598}]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.46%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[{"kind":"new","label":"New CVE","at":"2026-10-20T22:19:30.000Z","detail":{"score":"7.4","severity":"HIGH","publishedAt":"2026-10-20T22:19:29.570Z"},"summary":"New CVE, high severity (CVSS 7.4)."}],"references":[{"url":"https://github.com/openchoreo/openchoreo/commit/0e311468bb704b0dce7753b89c9d0204009285ca","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/commit/477031c6fece0666f144942fb02c0b579dacc0bb","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/commit/91e1e868eb8e0e67274109018d00a767b22eda14","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/commit/d5ed0ef62d9c9af7b05a72aed2bcbc0ac9d45426","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/pull/4596","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/pull/4618","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/pull/4626","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/pull/4627","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/releases/tag/v1.0.6","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/releases/tag/v1.1.7","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/releases/tag/v1.2.5","source":"security-advisories@github.com"},{"url":"https://github.com/openchoreo/openchoreo/security/advisories/GHSA-46r4-q7wv-32fc","source":"security-advisories@github.com"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-113727","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}