CVE-2026-50548
Sandbox escape: writable working_directory enables non-sandboxed RCE in Cursor pre-3.0
Is CVE-2026-50548 being exploited?
Not confirmed. CVE-2026-50548 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-50548?
CVE-2026-50548 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50548?
Yes. A fix has been recorded for CVE-2026-50548. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50548 affect?
CVE-2026-50548 affects Cursor (Code Editor) pre-3.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50548?
Upgrade to Cursor 3.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution by a malicious agent via writable_working_directory outside the sandbox; could overwrite cursorsandbox and run unsandboxed.
Immediate action required
- affected< 3.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.