Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege Coze account
-
DeliveryEnumerate or obtain foreign workflowID
-
ExploitPair own spaceID with victim workflowID
-
ExecutionInvoke save/canvas/batch_delete/test_run handlers
-
ImpactRead, run, overwrite or delete tenant workflows
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a valid authenticated account (any low-privilege tenant user) on a Coze Studio instance through version 0.5.1, plus knowledge or enumeration of a target's workflowID. Exploitation is performed against the save, update_meta, batch_delete, canvas, test_run and nodeDebug workflow API routes, where the server trusts the client-supplied workflowID without verifying it belongs to the caller's spaceID. Limiting factors: the attacker must already be authenticated (PR:L) so this is not usable by fully anonymous external attackers; realistic risk is highest on shared or multi-tenant deployments where untrusted users can register, and lower on single-tenant private installations. No user interaction, no special non-default configuration, and no elevated privileges are required beyond basic account access. |
| Impact | This is a genuine, actionable priority rather than a paper-high score. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a network-reachable, low-complexity attack needing only low privileges and no user interaction, which is fully consistent with the description: any authenticated tenant can reference another tenant's workflowID. The 8.7 (High) rating is driven by VC:H/VI:H (full cross-tenant read and overwrite/delete of workflows) with VA:L. Exploitability signals reinforce priority: a public POC/exploit exists (referenced on lasso.security) and the issue was reported by VulnCheck, a credible exploit-intelligence source. Counter-signals and gaps: there is NO EPSS score provided and NO SSVC decision data in the input, so automatability and probability of exploitation cannot be quantified here. The CVE is NOT in CISA KEV, so there is no evidence of active in-the-wild exploitation - POC availability must not be conflated with active exploitation. Net: a multi-tenant SaaS/self-hosted platform with a trivially exploitable cross-tenant authorization flaw and public exploit code warrants prompt patching, but the real-world blast radius is bounded by deployment footprint and the requirement that the attacker already hold a valid (low-privilege) account on the instance. |
| Exploit ScenarioDerived | An attacker signs up for or already holds a low-privilege account on a shared Coze Studio instance, then calls workflow API handlers (e.g. canvas or test_run) substituting a victim tenant's workflowID while keeping their own spaceID, reading or executing a competitor's proprietary workflow. By calling save, update_meta or batch_delete the same attacker can overwrite or permanently delete another tenant's workflows. Public exploit code is available (referenced via lasso.security and VulnCheck), lowering the barrier to weaponization. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
Coze Studio through 0.5.1 exposes cross-tenant workflow access because its workflow API trusts a client-supplied workflowID without verifying that the object belongs to the caller's space. An authenticated low-privilege user who knows or enumerates another tenant's workflowID can pair it with their own spaceID and read, run, overwrite, or delete that workflow via the save, update_meta, batch_delete, canvas, test_run, and nodeDebug routes. Publicly available exploit code exists, and exposure is highest on shared or multi-tenant deployments that allow untrusted users to register, while single-tenant private installations face lower practical risk.
RemediationAI
No vendor-released patch was identified at time of analysis, so remediation should begin with confirming whether a build later than 0.5.1 contains an object-level authorization fix and upgrading to it if available. Until then, enforce tenant isolation in front of the workflow API: reject save, update_meta, batch_delete, canvas, test_run, and nodeDebug requests where the supplied workflowID does not belong to the authenticated caller's spaceID, accepting the operational cost of maintaining a reliable space-to-workflow mapping. Disable open self-registration or restrict account and tenant creation to trusted administrators, which reduces exposure on multi-tenant instances but may break self-service onboarding; alternatively, run each tenant on an isolated Coze Studio instance, at higher infrastructure cost. Restrict network access to the workflow API to trusted networks or VPN, and monitor logs for mismatched spaceID/workflowID pairs so attempted exploitation is detected. Review the VulnCheck advisory at https://www.vulncheck.com/advisories/coze-studio-through-0.5.1-cross-space-workflow-idor-via-workflow-api-handlers and the source reference at https://github.com/coze-dev/coze-studio/blob/72cecff858a5a18662c5d9d1a4764c53ebc98317/backend/application/workflow/workflow.go#L303 for technical details, and apply a WAF or API-gateway virtual patch if one is available for these routes; note that virtual patching requires accurate request parsing and may miss encoded or unusual requests.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-639 (Authorization Bypass Through User-Controlled Key), a classic insecure direct object reference in Coze Studio's Go backend. The affected handlers in backend/application/workflow/workflow.go, around line 303, accept both spaceID and workflowID from the request and act on the workflow without an object-level check that the workflow's owning space matches the caller's space. That missing tenant-isolation control lets an authenticated user substitute a foreign workflowID in save, update_meta, batch_delete, canvas, test_run, and nodeDebug operations, turning low-privilege account access into cross-space reads, execution, metadata overwrite, or deletion. The CPE cpe:2.3:a:coze-dev:coze-studio:*:*:*:*:*:*:*:* is a wildcard entry and should be read with the CVE's 'through 0.5.1' scope. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L) confirms network reachability with low privileges and no user interaction, consistent with an authenticated multi-tenant API abuse rather than an anonymous pre-auth flaw.
Know when Coze Studio gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Network-reachable API, low complexity, and only a basic authenticated account (PR:L); full cross-tenant workflow read (C:H) and overwrite/delete (I:H) with limited availability impact (A:L).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Coze Studio through 0.5.1 contains an insecure direct object reference vulnerability in workflow.go that allows authenticated users to access other spaces' workflows by supplying foreign workflowIDs. Attackers can pair their own spaceID with another tenant's workflowID in save, update_meta, batch_delete, canvas, test_run and nodeDebug routes to read, run, overwrite or delete workflows.
Technical POC Analysis
CWE-639, Authorization Bypass Through User-Controlled Key - a cross-tenant IDOR in the workflow API of Coze Studio (coze-dev/coze-studio).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Coze Studio deployments at or below version 0.5.1 contain a cross-tenant isolation failure in the workflow API, letting one tenant read, execute, overwrite, or delete another tenant's workflows. Organizations hosting Coze Studio for multiple customers or untrusted user populations face potential exposure of proprietary automation logic and destructive modification of business processes across customer boundaries. Single-tenant, privately operated instances carry materially lower practical risk, so leadership attention should focus on shared and externally accessible deployments.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce server-side ownership validation of workflowID against the caller's spaceID on all workflow routes; disable or gate untrusted user registration and restrict the save, update_meta, batch_delete, canvas, test_run, and nodeDebug endpoints to trusted operators; segment multi-tenant deployments into isolated per-tenant instances; monitor and alert on cross-tenant object access patterns in API logs.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in Coze Studio RCE and IDOR Vulnerabilities
View all 2More in Coze Studio
View allImproper authorization in Coze Studio through 0.5.1 lets an authenticated user (CVSS PR:L) abuse the workflow SQL custom
Server-side request forgery in Coze Studio through version 0.5.1 allows an authenticated user who can register or config
SQL injection in ByteDance coze-studio up to version 0.5.1 allows authenticated remote attackers to manipulate the Execu
EUVD-2026-104691
GHSA-w9wj-jq72-68p2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB