dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-48124

HIGH · 8.5 CVSS v4.0 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In versions prior to 3.0.0, Cursor Desktop would execute Claude hook commands defined in .claude/settings.local.json without requiring dedicated user approval. A malicious or compromised workspace could configure hooks that execute arbitrary local commands in the user's context when an agent turn ends, enabling sandbox escape, persistence, or local data access.

MitigationUpgrade Cursor Desktop to version 3.0.0 or later to obtain the fix. Additionally, review any .claude/settings.local.json files in workspaces for suspicious or unexpected hook configurations before opening them.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Cursor version
    Open Cursor Desktop, go to Help > About, or check the application package metadata to find the installed version number
    Affected if Version is earlier than 3.0.0 (e.g., 2.x.x, 1.x.x)
  2. Locate Claude settings file
    Navigate to the user home directory and look for .claude/settings.local.json, or find it in the workspace root .claude/ directory
    Affected if This file exists in the user's home directory or project directory
  3. Inspect for hook configurations
    Open .claude/settings.local.json and examine the JSON for a 'hooks' key or similar configuration section that defines command executions
    Affected if The file contains hook definitions (e.g., 'hooks', 'onTurnEnd', or similar keys with command arrays)
  4. Identify executable hook commands
    Within any found hook configuration, review the command values to determine if they execute local system commands, scripts, or binaries
    Affected if Hooks contain commands that execute local binaries, scripts, or shell commands (not just API calls)

User is affected if running Cursor version before 3.0.0 and a .claude/settings.local.json file exists with configured hook commands that execute locally.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cursor Desktop to version 3.0.0 or later to obtain the fix. Additionally, review any .claude/settings.local.json files in workspaces for suspicious or unexpected hook configurations before opening them.

Recommended fix High confidence

3.0.0

  1. Upgrade Cursor Desktop to version 3.0.0 or later
  2. Verify the upgrade by checking the Cursor version in the application about section
  3. After upgrading, review .claude/settings.local.json files in workspaces for any suspicious hook configurations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48124 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data