Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4amended

OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs

CVE-2026-113727GHSA-46r4-q7wv-32fc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/openchoreo/openchoreo 1.2.5, 1.1.7, 1.0.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
EPSS
  • CVE-2026-113727: 0.46% estimated exploitation activity in the next 30 days; percentile 40.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The OpenChoreo API server authorized PUT .../workflowruns/{runName} against ownership metadata taken from the request body, while the object it actually mutated was selected by the URL path. Nothing forced the two to agree. A WorkflowRun's membership in a project and component is carried entirely by its openchoreo.dev/project and openchoreo.dev/component labels. Because the workflowrun:update check read those labels from the submitted object rather than the stored one, a caller holding workflowrun:update on one component could name a run belonging to a different project or component in the URL, supply labels for the component they legitimately control, pass the check, and have the unrelated run rewritten with their own ownership labels. The namespace is taken from the URL and feeds both the authorization check and the Kubernetes read, so it cannot diverge. This is cross-project and cross-component escalation inside a single namespace, not a cross-tenant issue. Impact…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-46r4-q7wv-32fc

  2. Revision 1 · created ·

    Published from osv record GHSA-46r4-q7wv-32fc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-113727

Advisory: OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs
IDs: CVE-2026-113727, GHSA-46r4-q7wv-32fc
Record: https://patchnext.com/advisories/cve-2026-113727 (revision 2, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openchoreo/openchoreo 1.2.5, 1.1.7, 1.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openchoreo/openchoreo: affected >= 1.0.0, < 1.0.6; >= 1.1.0, < 1.1.7; >= 1.2.0, < 1.2.5; fixed in 1.0.6, 1.2.5, 1.1.7

## Suggested inspection (read-only)
- Go github.com/openchoreo/openchoreo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openchoreo/openchoreo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-46r4-q7wv-32fc (OSV record GHSA-46r4-q7wv-32fc lists affected ranges: Go github.com/openchoreo/openchoreo >=1.0.0 =1.1.0 =1.2.0 <1.2.5 (fixed))
- Verified: https://github.com/advisories/GHSA-46r4-q7wv-32fc (GitHub-reviewed advisory GHSA-46r4-q7wv-32fc lists affected ranges: Go github.com/openchoreo/openchoreo >=1.0.0 =1.1.0 =1.2.0 <1.2.5)

Commands are suggestions: review each one before running it.

Loading voting…