Skip to main content

OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs (CVE-2026-113727)

0
High
Published: 10/21/2026 (10/21/2026, 16:29:53 UTC)
Source: GCVE Database
Product: github.com/openchoreo/openchoreo

Description

OpenChoreo contains an authorization bypass vulnerability in its API server's WorkflowRun update endpoint. The server authorizes updates based on ownership metadata from the request body rather than the stored object, allowing an authenticated user with update rights on one component to rewrite ownership labels of a WorkflowRun belonging to another component within the same namespace. This leads to unauthorized access to build logs, Kubernetes events, and the ability to delete runs. The issue affects OpenChoreo versions 1.0.0 through 1.0.5, 1.1.0 through 1.1.6, and 1.2.0 through 1.2.4. Patches are available in versions 1.0.6, 1.1.7, and 1.2.5.

CVSS v3.1

Score 7.4high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Affected software

Goghsa
github.com/openchoreo/openchoreo
Affected versions
>=1.0.0 <1.0.6
Goghsa
github.com/openchoreo/openchoreo
Affected versions
>=1.1.0 <1.1.7
Goghsa
github.com/openchoreo/openchoreo
Affected versions
>=1.2.0 <1.2.5

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/21/2026, 20:17:53 UTC

Technical Analysis

The OpenChoreo API server's PUT endpoint for updating WorkflowRuns authorized requests by checking ownership labels from the submitted request body instead of the stored object. Since the actual object mutated is selected by the URL path, this mismatch allowed an authenticated user with 'workflowrun:update' permission on one component to specify a WorkflowRun belonging to another project or component in the URL, supply labels for their own component in the request body, pass authorization, and overwrite the unrelated run's ownership labels. This cross-project and cross-component escalation within a single namespace enables the attacker to gain legitimate access to the victim's WorkflowRun, including reading build logs and Kubernetes events, deleting the run, and modifying workflow parameters. The vulnerability requires authenticated access with update permissions and knowledge of the target run's name. The issue is fixed by deriving ownership attributes from the stored WorkflowRun and making ownership labels immutable on update. Versions 1.0.0 through 1.0.5, 1.1.0 through 1.1.6, and 1.2.0 through 1.2.4 are affected, with fixes in 1.0.6, 1.1.7, and 1.2.5.

Potential Impact

An attacker with authenticated access and 'workflowrun:update' permission on a component can escalate privileges within a namespace by rewriting ownership labels of WorkflowRuns belonging to other projects or components. This grants unauthorized read access to sensitive build logs containing potentially confidential information such as source paths and credentials, read access to Kubernetes events, and the ability to delete WorkflowRuns. Additionally, the attacker can manipulate workflow parameters and cause workflow runs to enter error states or bypass component validation. The impact affects confidentiality, integrity, and availability of WorkflowRun objects within the namespace.

Mitigation Recommendations

A patch is available and should be applied by upgrading to OpenChoreo versions 1.0.6, 1.1.7, or 1.2.5 depending on the release line in use. No configuration changes are required after upgrading. If immediate upgrade is not possible, restrict the 'workflowrun:update' permission to trusted principals only by auditing and adjusting AuthzRole and ClusterAuthzRole bindings. Pay particular attention to roles such as 'workload-publisher' and 'admin' which include this permission. Treat credentials bound to these roles as highly privileged and protect them accordingly.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-46r4-q7wv-32fc
Osv Schema Version
1.4.0
Aliases
["CVE-2026-113727"]
Ecosystems
["Go"]
Database Specific Severity
HIGH
Cvss Version
3.1

Threat ID: 6ad91cca4d27ba8daafaa0ff

Added to database: 10/21/2026, 20:12:58 UTC

Last enriched: 10/21/2026, 20:17:53 UTC

Last updated: 10/21/2026, 20:17:53 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses