dbcve.org
CursorApplication · Anysphere

CVE-2026-26268

CRITICAL · 9.9 CVSS v3.1 Published 2026-02-13
Fix available
A fix is available. Upgrade to 2.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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. Sandbox escape via writing .git configuration was possible in versions prior to 2.5. A malicious agent (ie prompt injection) could write to improperly protected .git settings, including git hooks, which may cause out-of-sandbox RCE next time they are triggered. No user interaction was required as Git executes these commands automatically. Fixed in version 2.5.

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

A sandbox escape vulnerability in Cursor (versions prior to 2.5) allowed malicious AI agents via prompt injection to write to improperly protected .git configuration files, including git hooks. Since Git automatically executes these hooks, this enables remote code execution outside the sandbox without any user interaction.

MitigationUpgrade Cursor to version 2.5 or later to obtain the fix for this sandbox escape vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CursorApplication
Affected:< 2.5

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 installed Cursor version
    Open Cursor, then go to Cursor > About Cursor (or check the version in the application menu) to view the currently installed version number
    Affected if The displayed version is below 2.5 (e.g., 2.4.x, 2.3.x, etc.)
  2. Verify AI agent feature is accessible
    Locate the AI agent feature in Cursor (typically in the sidebar or via a chat/agent interface). Determine if the agent feature is active or can be invoked
    Affected if The AI agent feature is present and functional in the installed version
  3. Inspect .git hooks directory permissions
    Open a terminal and navigate to any project directory. Check the .git/hooks directory for permissions: ls -la .git/hooks/ and examine if hooks are present or were recently modified
    Affected if The .git/hooks directory contains executable scripts or shows recent modifications that were not initiated by the user
  4. Review git configuration file integrity
    Check .git/config file in repositories for unexpected changes: cat .git/config and compare against known-good configurations or version control history
    Affected if The .git/config file contains unexpected entries, especially in the core.hooksPath setting or contains hooks pointing to external locations

You are affected if your Cursor version is below 2.5 and the AI agent feature can write files to .git directories in your projects.

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
Upgrade available Upgrade to 2.5 or later
Fixed in 2.5
Interim mitigation

Upgrade Cursor to version 2.5 or later to obtain the fix for this sandbox escape vulnerability.

Recommended fix High confidence

Cursor 2.5

  1. Check current Cursor version by clicking Cursor > About Cursor
  2. Update Cursor to version 2.5 by using the built-in update mechanism (Cursor > Check for Updates) or downloading version 2.5 from the official Cursor website
  3. Verify the installed version is 2.5 or later by checking About Cursor

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

Fix this in Cursor Scoped from the published advisory
  • Consultation0.5 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.3 h
1.8 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26268 — 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-26268 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