# CVE-2026-48124: Cursor Desktop sandbox escape via Claude hook configuration

> Attackers can execute arbitrary local commands via malicious workspace hook configurations, leading to sandbox escape and data access.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026

## What is CVE-2026-48124?

CVE-2026-48124 is a high-severity code injection vulnerability in cursor, published on 15 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cursor is a code editor built for programming with AI. In versions prior to 3.0.0, the Cursor Desktop could execute workspace-defined Claude hook commands from .claude/settings.local.json without dedicated user approval. A malicious workspace or agent-created file could configure hooks that run local commands in the user's context when an agent turn ends. This could allow sandbox escape, persistence across turns, local data access, or follow-on compromise. This issue has been fixed in version 3.0.0.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-48124 being exploited?

There is no known exploitation of CVE-2026-48124 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48124 is a high-severity code injection vulnerability in cursor, published on 15 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-48124 in the wild and no public exploit code.

Affected product: cursor. 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-48124/ (Markdown: https://insights.sbomify.com/CVE-2026-48124/index.md)
```

## Sources

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

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