Coze Studio versions up to 0.5.1 contain an insecure direct object reference flaw in workflow.go that lets an authenticated user supply a foreign workflow ID alongside their own space ID to target a workflow belonging to any other space. The flaw spans several API routes—save, update_meta, batch_delete, canvas, test_run and nodeDebug—allowing the attacker to read, execute, overwrite, or delete the target workflow. This grants an attacker the ability to alter the logic and behavior of another tenant’s automated processes, potentially leading to data leakage, unauthorized actions, or disruption of services.

Affected vendor is coze-dev, product Coze Studio, for all releases up to and including 0.5.1. The issue resides in the workflow.go source code and applies to any authenticated user exposed through the exposed Workflow API handlers.

The CVSS score of 8.7 reflects a high severity with full scope ranging from confidentiality, integrity, and availability impacts. EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, but the fact that it requires only authentication and the ability to guess or enumerate workflow IDs keeps it exploitable in practice. Attackers would need to identify a valid workflow ID from another space and combine it with their own space ID when calling the affected routes; if successful they can gain full control over the target workflow. This makes the vulnerability a significant risk, especially in multi-tenant deployments where tenants are not otherwise isolated.