dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-32018

HIGH · 8.0 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 0.45.0 through 0.48.6, the Cursor app introduced a regression affecting the set of file paths the Cursor Agent is permitted to modify automatically. Under specific conditions, the agent could be prompted, either directly by the user or via maliciously crafted context, to automatically write to files outside of the opened workspace. This behavior required deliberate prompting, making successful exploitation highly impractical in real-world scenarios. Furthermore, the edited file was still displayed in the UI as usual for user review, making it unlikely for the edit to go unnoticed by the user. This vulnerability is fixed in 0.48.7.

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

Cursor versions 0.45.0-0.48.6 contained a regression where the AI agent could be deliberately prompted (by user or malicious context) to write files outside the permitted workspace boundaries. The agent bypassed workspace restrictions, allowing file writes to arbitrary paths on the filesystem while still displaying edits in the UI for review.

MitigationUpgrade Cursor to version 0.48.7 or later to obtain the vendor patch. No additional configuration required as the fix is built into the application.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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. Determine installed Cursor version
    Open Cursor, then go to Cursor > About Cursor (on macOS) or Help > About (on Windows/Linux) to view the version number. Alternatively, check the application installation directory or package manager for the installed version.
    Affected if The version displayed is 0.45.0, 0.45.1, 0.45.2, 0.45.3, 0.45.4, 0.45.5, 0.45.6, 0.46.0 through 0.46.x, 0.47.0 through 0.47.x, or 0.48.0 through 0.48.6 (any version from 0.45.0 up to and including 0.48.6).
  2. Verify the version is within affected range
    Compare your installed version number to the affected range: 0.45.0 <= version <= 0.48.6
    Affected if Your Cursor version falls within 0.45.0 to 0.48.6 inclusive.
  3. Confirm AI agent feature is in use
    Determine whether you use Cursor's AI agent features (such as Composer, Chat with agent mode, or AI-edit capabilities that can write files). This vulnerability only affects environments where the AI agent writes files.
    Affected if You actively use Cursor's AI agent to generate or edit files, as the flaw allows the agent to bypass workspace restrictions.

You are affected if your installed Cursor version is 0.45.0 through 0.48.6 and you use the AI agent feature that can write files to the filesystem.

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 to version 0.48.7 or later to obtain the vendor patch. No additional configuration required as the fix is built into the application.

Recommended fix High confidence

0.48.7

  1. Open Cursor application
  2. Check current version: On macOS, go to Cursor > About Cursor; on Windows/Linux, go to Help > About
  3. If version is between 0.45.0 and 0.48.6 (inclusive), initiate the update
  4. Update to version 0.48.7 or later via the application's built-in update mechanism, or download the latest version from the official Cursor website

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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