{"answers":{"affected":"6 open source packages ship an affected version, including github.com/openchoreo/openchoreo.","exploited":"There is no known exploitation of CVE-2026-113727 in the wild and no public exploit code.","fix":"Upgrade github.com/openchoreo/openchoreo to a fixed version for your release line: 1.0.6, 1.1.7 or 1.2.5.","what":"CVE-2026-113727 is a high-severity vulnerability in openchoreo, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-113727 and fix it if it is affected.\n\nWhat it is: CVE-2026-113727 is a high-severity vulnerability in openchoreo, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-113727 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/openchoreo/openchoreo (Go): affected from 1.0.0; fixed in 1.0.6\n- github.com/openchoreo/openchoreo (Go): affected from 1.0.0; fixed in 1.0.6\n- github.com/openchoreo/openchoreo (Go): affected from 1.1.0; fixed in 1.1.7\n- github.com/openchoreo/openchoreo (Go): affected from 1.1.0; fixed in 1.1.7\n- github.com/openchoreo/openchoreo (Go): affected from 1.2.0; fixed in 1.2.5\n- github.com/openchoreo/openchoreo (Go): affected from 1.2.0; fixed in 1.2.5\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-113727/ (Markdown: https://insights.sbomify.com/CVE-2026-113727/index.md)","id":"CVE-2026-113727","markdown":"https://insights.sbomify.com/CVE-2026-113727/index.md","name":"CVE-2026-113727","record":{"aliases":["GHSA-46r4-q7wv-32fc"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs","id":"CVE-2026-113727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2026"},"n_packages":6,"n_references":12,"next":{"headline":"Bulwark Webmail: DNS-rebinding SSRF in public iCalendar fetch endpoint","id":"CVE-2026-113728"},"packages":[{"ecosystem":"Go","fixed":["1.0.6"],"introduced":["1.0.0"],"last_affected":[],"package":"github.com/openchoreo/openchoreo","purl":null,"source":"GHSA-46r4-q7wv-32fc"},{"ecosystem":"Go","fixed":["1.0.6"],"introduced":["1.0.0"],"last_affected":[],"package":"github.com/openchoreo/openchoreo","purl":"pkg:golang/github.com/openchoreo/openchoreo","source":"GHSA-46r4-q7wv-32fc"},{"ecosystem":"Go","fixed":["1.1.7"],"introduced":["1.1.0"],"last_affected":[],"package":"github.com/openchoreo/openchoreo","purl":null,"source":"GHSA-46r4-q7wv-32fc"},{"ecosystem":"Go","fixed":["1.1.7"],"introduced":["1.1.0"],"last_affected":[],"package":"github.com/openchoreo/openchoreo","purl":"pkg:golang/github.com/openchoreo/openchoreo","source":"GHSA-46r4-q7wv-32fc"},{"ecosystem":"Go","fixed":["1.2.5"],"introduced":["1.2.0"],"last_affected":[],"package":"github.com/openchoreo/openchoreo","purl":null,"source":"GHSA-46r4-q7wv-32fc"},{"ecosystem":"Go","fixed":["1.2.5"],"introduced":["1.2.0"],"last_affected":[],"package":"github.com/openchoreo/openchoreo","purl":"pkg:golang/github.com/openchoreo/openchoreo","source":"GHSA-46r4-q7wv-32fc"}],"prev":{"headline":"virtualenv activate runs commands from the environment name in zsh with PROMPT_SUBST","id":"CVE-2026-113726"},"products":["openchoreo"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-23","vendors":["openchoreo"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-113727/"}