Live › vulnerability › CVE-2026-77934
Go to dashboardCoze Studio before 0.5.0 runs workflow code nodes in an unsandboxed python3 subprocess by default. A registered user can bypass the regex import filter with __import__('subprocess') to run commands, reading environment variables, model API keys, and access to MySQL, MinIO, Redis and etcd.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| coze-studio | github | >= 0, < 0.5.0 | 0.5.0 |
local or unset on a pre-0.5.0 install means exposed; sandbox means workflow code nodes run in deno+pyodidedocker ps | grep coze-studio-server (cozedev/coze-studio-server:<tag> older than 0.5.0 is affected)0.5.0 or later (0.5.1 is current in the release list I read)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Coze Studio before 0.5.0 contains an insecure default configuration that allows any registered user to execute commands by running workflow code nodes in an unsandboxed python3 subprocess. Attackers can bypass the regex import filter with import('subprocess') to run commands, stealing environment variables, model API keys, and accessing MySQL, MinIO, Redis and etcd.
This page as .md · .json · in your agent: get_signal("CVE-2026-77934")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.