# CVE-2026-77934: Coze Studio before 0.5.0 RCE via Unsandboxed Local Python Code Runner


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-46jr-m373-8hpx

## What is CVE-2026-77934?

CVE-2026-77934 is a high-severity vulnerability in coze-dev coze-studio, published on 20 Oct 2026. 

### Official description

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.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2026-77934?


## How do I fix CVE-2026-77934?

No fix has been published for CVE-2026-77934 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77934 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77934 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77934 and fix it if it is affected.

What it is: CVE-2026-77934 is a high-severity vulnerability in coze-dev coze-studio, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77934 exists.

Affected product: coze-dev coze-studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77934/ (Markdown: https://insights.sbomify.com/CVE-2026-77934/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77934
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77934
- OSV: https://osv.dev/vulnerability/CVE-2026-77934

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77934/
Summaries are generated and may contain mistakes; the official description above is the record.