cve.bz

CVE-2026-113727 openchoreo openchoreo

7.4 highEPSS 0.5%Fix available

High (7.4) in openchoreo openchoreo. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/openchoreo/openchoreo 1.0.6, 1.1.7, 1.2.5.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-113727 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113727?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113727?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-113727 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
openchoreo>= 1.0.0, < 1.0.6
openchoreo>= 1.1.0, < 1.1.7
openchoreo>= 1.2.0, < 1.2.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-46r4-q7wv-32fcGogithub.com/openchoreo/openchoreo>=1.0.0 <1.0.61.0.6
GHSA-46r4-q7wv-32fcGogithub.com/openchoreo/openchoreo>=1.1.0 <1.1.71.1.7
GHSA-46r4-q7wv-32fcGogithub.com/openchoreo/openchoreo>=1.2.0 <1.2.51.2.5
GO-2026-6825Gogithub.com/openchoreo/openchoreo>=1.0.0 <1.0.6
>=1.1.0 <1.1.7
>=1.2.0 <1.2.5
1.0.6, 1.1.7, 1.2.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE.

References

Check your stackJSON