CVE Intelligence
High Access control

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

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.

Published Oct 20, 2026 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.43%
ahead of 37% of scored CVEs · Oct 22, 2026
Affects
Openchoreo
Openchoreo and 1 more
CVSS base
7.4
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Go Github.com/openchoreo/openchoreo: fixed in version 1.0.6 — github.com (GitHub Security Advisories)
  • Go Github.com/openchoreo/openchoreo: fixed in version 1.1.7 — github.com (GitHub Security Advisories)
  • Go Github.com/openchoreo/openchoreo: fixed in version 1.2.5 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Openchoreo Openchoreo, Go Github.com/openchoreo/openchoreo).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Openchoreo Openchoreo version >= 1.0.0, < 1.0.6version >= 1.1.0, < 1.1.7version >= 1.2.0, < 1.2.5 Vulnerable CVE Program (cve.org) e CISA ADP
Go Github.com/openchoreo/openchoreo ≥ 1.0.0 and < 1.0.6≥ 1.1.0 and < 1.1.7≥ 1.2.0 and < 1.2.5 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.4 CVSS 3.1 High 3.1 3.7 security-advisories@github.com via NIST National Vulnerability Database
7.4 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.4 CVSS 3.1 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-639 · Authorization Bypass Through User-Controlled Key (IDOR)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 21, 2026 → Oct 22, 2026 · 2 reading(s) · max 0.43%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Fix documented
    Oct 22, 2026 · GitHub Security Advisories
  • Affected products added · go/github.com/openchoreo/openchoreo
    Oct 22, 2026 · GitHub Security Advisories
  • Source status changed · Received → Awaiting Analysis
    Oct 22, 2026 · NIST National Vulnerability Database
  • Affected products added · openchoreo/openchoreo
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 20, 2026
  • CVSS changed · 7.4
    Oct 20, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 20, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 20, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 20, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 22, 2026 – Oct 22, 2026
  • 1× Official description updated · Oct 20, 2026 – Oct 20, 2026

References

14 on the record

Elsewhere on this site

Openchoreo
every CVE for this vendor
Access control
same class
CWE-639
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-73842 OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation Aug 13, 2026
  • CVE-2026-73843 OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs Aug 13, 2026
  • CVE-2026-73667 OpenChoreo: Authenticated OS command injection via OpenChoreo Workflow Plane templates enables code execution in privileged pods Aug 13, 2026
  • CVE-2026-73840 OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass) Aug 13, 2026
  • CVE-2026-73841 OpenChoreo: Cross-project command execution and wirelog view access via OpenChoreo openchoreo-api exec and wirelogs endpoints Aug 13, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-113727 is "OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs", rated High. It affects Openchoreo (Openchoreo); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.43% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.