Cursor Desktop sandbox escape via agent-controlled working directory
CriticalCVE-2026-50548 · Published Jun 5, 2026
### Summary Cursor runs agent terminal commands in a sandbox by default, and the sandbox grants write access to the command's working directory. A flaw was identified in how the agent could modify the `working_directory` parameter, which could cause the sandbox to include writable paths outside the intended workspace. ### Impact A malicious agent could set `working_directory` to a sensitive location and write arbitrary files outside the workspace under the user's privileges. This enables non-sandboxed Remote Code Execution — for example by overwriting the `cursorsandbox` helper so later commands run unsandboxed — with no user interaction beyond a benign prompt. ### Remediation Update Cursor to version 3.0. The sandbox no longer grants write access based on an agent-controlled working directory. ### Credit Cato AI Labs
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Cursor Product | < 3.0 | 3.0 |
Details and references
- Severity from
- GitHub (reviewed advisory)
More Cursor advisories
All Cursor| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jul 14 | Sandbox escape via tampered Python virtual environments | High | 3.1.2 |
| Jul 14 | Sandbox escape via launching privileged containers | High | No fix yet |
| Jul 6 | Cloud Agent Browser Sandbox Escape | High7.7 | Fixedon03/31/2026 |
| Jun 5 | Cursor Desktop sandbox escape via symlink and failed path canonicalization | Critical | 3.0 |
| May 21 | Cursor Desktop sandbox escape via Claude hook configuration | High8.5 | 3.0.0 |
| Mar 9 | Arbitrary Code Execution via Prompt Injection and Whitelist Bypass | High | 2.0 |