Skip to main content
Vulnerability Database/CVE-2026-113727

CVE-2026-113727: OpenChoreo Privilege Escalation Vulnerability

CVE-2026-113727 is a privilege escalation flaw in OpenChoreo that allows authenticated attackers to manipulate workflow run ownership labels and gain unauthorized access. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-113727 Overview

CVE-2026-113727 is a broken access control vulnerability in OpenChoreo, a developer platform for Kubernetes. The flaw affects the PUT .../workflowruns/{runName} endpoint, which authorizes requests using ownership labels submitted in the request body rather than labels stored on the target resource. An authenticated caller with workflowrun:update permission for any project or component in a namespace can rewrite another run's ownership labels, gaining the ability to read logs, delete the run, modify pending workflow parameters, or force a permanent ComponentValidationFailed state. The issue is tracked as CWE-639: Authorization Bypass Through User-Controlled Key and is fixed in versions 1.0.6, 1.1.7, and 1.2.5.

Critical Impact

Authenticated tenants in a shared namespace can hijack ownership of WorkflowRun objects belonging to other projects or components, enabling data disclosure, tampering, and denial of service against build pipelines.

Affected Products

  • OpenChoreo versions 1.0.0 through 1.0.5
  • OpenChoreo 1.1.0 through 1.1.6
  • OpenChoreo 1.2.0 through 1.2.4

Discovery Timeline

  • 2026-10-20 - CVE-2026-113727 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-113727

Vulnerability Analysis

The vulnerability resides in the UpdateWorkflowRun handler within internal/openchoreo-api/services/workflowrun/service_authz.go. The authorization layer constructs its hierarchy check from the openchoreo.dev/project and openchoreo.dev/component labels supplied in the incoming request body, while the stored WorkflowRun is selected by the {runName} URL path parameter and namespace. The two inputs are never cross-validated.

An attacker who already possesses workflowrun:update on any project or component within the namespace can submit labels pointing at a scope they legitimately control, while naming a victim's run in the path. The authorization check passes, and the update rewrites the stored labels. All subsequent reads and mutations on that run then evaluate against the attacker's scope, delivering access to build logs, Kubernetes events, deletion rights, and the ability to modify spec.workflow.parameters while the run is still pending.

Root Cause

The handler trusted client-supplied ownership metadata for the authorization decision. The patch introduces a fetch of the stored resource before the authz.Check call, so the hierarchy is derived from existing.Labels rather than wfRun.Labels. The scope of the issue is bounded by the namespace, which still comes from the URL, so the flaw is cross-project or cross-component within a single namespace rather than cross-tenant.

Attack Vector

Exploitation requires network access to the OpenChoreo API and valid credentials with workflowrun:update on at least one project or component in the target namespace. The attacker issues a PUT to /workflowruns/{victimRunName} and sets the body's project and component labels to a scope they own. No user interaction is needed.

go
// Patch excerpt - internal/openchoreo-api/services/workflowrun/service_authz.go
// Source: https://github.com/openchoreo/openchoreo/commit/0e311468bb704b0dce7753b89c9d0204009285ca
func (s *workflowRunServiceWithAuthz) UpdateWorkflowRun(ctx context.Context, namespaceName string, wfRun *openchoreov1alpha1.WorkflowRun) (*openchoreov1alpha1.WorkflowRun, error) {
    if wfRun == nil {
        return nil, fmt.Errorf("workflow run cannot be nil")
    }
    // Fetch the existing workflow run to get owner info for authz, mirroring the pattern
    // used by workload/service_authz.go and friends.
    existing, err := s.internal.GetWorkflowRun(ctx, namespaceName, wfRun.Name)
    if err != nil {
        return nil, err
    }
    if err := s.authz.Check(ctx, services.CheckRequest{
        Action:       authz.ActionUpdateWorkflowRun,
        ResourceType: resourceTypeWorkflowRun,
        ResourceID:   existing.Name,
        Hierarchy:    constructHierarchyForAuthzCheck(namespaceName, existing.Labels),
        Context: authz.Context{
            Resource: authz.ResourceAttribute{
                Workflow: formatWorkflowAttr(namespaceName, existing.Spec.Workflow.Kind, existing.Spec.Workflow.Name),
            },
        },
    }); err != nil {

The fix replaces wfRun.Name and wfRun.Labels with values pulled from the stored existing object, closing the trust gap between the authorization check and the resource being modified.

Detection Methods for CVE-2026-113727

Indicators of Compromise

  • PUT requests to /workflowruns/{runName} where the body's openchoreo.dev/project or openchoreo.dev/component labels differ from the labels previously stored on that run.
  • WorkflowRun objects whose ownership labels change without a corresponding create event from the same identity.
  • Unexpected transitions of WorkflowRun objects into a ComponentValidationFailed state after an update from a user outside the owning project.

Detection Strategies

  • Compare the spec.workflow and label fields of each incoming WorkflowRun update against the stored object and alert on mismatches between body-supplied scope and persisted scope.
  • Audit the OpenChoreo API access log for workflowrun:update actions where the caller's authorized project or component does not match the stored run's labels.
  • Correlate Kubernetes audit events for WorkflowRun label mutations with the authenticated identity recorded in the API gateway.

Monitoring Recommendations

  • Enable verbose authorization logging on the openchoreo-api service and forward events to a centralized log platform for retention and search.
  • Track read access to build logs and Kubernetes events segmented by project and component to surface anomalous access patterns.
  • Alert on repeated 2xx responses to PUT /workflowruns/* from identities that have not previously created runs in the targeted project.

How to Mitigate CVE-2026-113727

Immediate Actions Required

  • Upgrade OpenChoreo to 1.0.6, 1.1.7, or 1.2.5 depending on your current minor version.
  • Review historical WorkflowRun label changes to identify runs whose ownership was rewritten prior to the upgrade.
  • Rotate any secrets or tokens that may have been exposed through unauthorized access to build logs.

Patch Information

The maintainers shipped the fix in OpenChoreo v1.0.6, v1.1.7, and v1.2.5. The authoritative advisory is GHSA-46r4-q7wv-32fc. Core commits include 0e31146, 477031c, 91e1e86, and d5ed0ef, delivered via pull requests #4596, #4618, #4626, and #4627.

Workarounds

  • Restrict workflowrun:update role bindings so that only project owners hold the permission within a given namespace.
  • Separate independent projects and components into distinct Kubernetes namespaces to eliminate the cross-project attack surface.
  • Place an authorizing proxy in front of the OpenChoreo API that validates body-supplied project and component labels against the authenticated identity before forwarding the request.
bash
# Upgrade example using Helm
helm repo update openchoreo
helm upgrade openchoreo openchoreo/openchoreo --version 1.2.5

# Verify the running version
kubectl -n openchoreo-system get deploy openchoreo-api \
  -o jsonpath='{.spec.template.spec.containers[0].image}'

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.