Coze Studio Users Face High-Risk Command Execution Flaw Before 0.5.0
An insecure default in Coze Studio allows registered users to run unsandboxed code, risking API key theft and database access until version 0.5.0 is deployed.
Key points
- CVE-2026-77934 carries a CVSS score of 8.7, rated high severity by the National Vulnerability Database.
- The flaw exists in Coze Studio versions prior to 0.5.0 and allows command execution via workflow nodes.
- Attackers can bypass import filters to access sensitive data including MySQL, Redis, and etcd credentials.
Coze Studio versions before 0.5.0 contain an insecure default configuration that exposes organizations to arbitrary code execution risks. According to the National Vulnerability Database, the flaw allows any registered user to run commands through unsandboxed Python subprocesses. This vulnerability stems from the default setting rather than a complex exploit chain, making it accessible to registered users. The issue affects the coze-dev coze-studio package specifically.
How it unfolded
- The National Vulnerability Database recorded CVE-2026-77934 with a high severity rating of 8.7.
- Researchers identified that the application uses an unsandboxed python3 subprocess for workflow code nodes.
- Attackers were found to bypass the regex import filter using the __import__('subprocess') method.
- The vulnerability enables access to environment variables, model API keys, and internal databases like MySQL.
Who is affected
Organizations using Coze Studio before version 0.5.0 are directly impacted by this vulnerability. The National Vulnerability Database identifies the affected component as coze-dev coze-studio. Any instance running a version lower than 0.5.0 is susceptible to the insecure default configuration. This includes development and production environments where registered users have access to workflow creation features. The flaw allows any registered user to execute commands via workflow code nodes.
Our take on the response
The National Vulnerability Database highlights the severity of default configurations in modern development tools. By allowing unsandboxed execution by default, the software exposes sensitive infrastructure components to internal threats. This underscores the need for strict isolation in code execution environments. The ability to bypass import filters suggests that basic security controls were insufficient against determined users. Organizations must treat this as a high-priority configuration issue rather than a minor bug.
Who needs to act first
Teams should prioritize updating systems that host sensitive data or connect to critical databases. Check inventory for any Coze Studio instances running versions below 0.5.0 immediately. Isolate affected workflows from production environments to prevent accidental execution of malicious code. Review access logs for any unusual workflow activity by registered users in the past week. Ensure that backup procedures are current before applying any configuration changes or updates. Limit user permissions to reduce the attack surface while a fix is deployed.
Background: Exploit chains
An exploit chain is a sequence of connected attacks where each step enables the next. Attackers use low-risk entry points to gain initial access, then move laterally to reach high-value targets. Breaking any single link stops the entire chain.
Read the full guide: Exploit Chains Explained: How Attackers String Vulnerabilities Together
What to do and how to stay safe: Coze Studio
- Verify the installed version of Coze Studio on all servers and workstations against the 0.5.0 threshold.
- Audit workflow code nodes for any use of subprocess imports or external command executions.
- Rotate any environment variables, API keys, or database credentials that may have been exposed.
- Monitor logs for unauthorized access attempts to MySQL, MinIO, Redis, or etcd services.
Step-by-step guide: Vulnerability Prioritization: How to Rank Risks Without Wasting Time
General security guidance from the Patch Observer newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-77934?
The National Vulnerability Database rates the vulnerability at 8.7, which is classified as high severity.
Which versions of Coze Studio are affected?
All versions of Coze Studio before 0.5.0 are affected by this insecure default configuration flaw.
Can external attackers exploit this vulnerability?
The source material states that any registered user can execute commands, implying internal access is required.
