CVE-2025-61589
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 · uneditedCursor is a code editor built for programming with AI. In versions 1.6 and below, Mermaid (a to render diagrams) allows embedding images which then get rendered by Cursor in the chat box. An attacker can use this to exfiltrate sensitive information to a third-party attacker controlled server through an image fetch after successfully performing a prompt injection. A malicious model (or hallucination/backdoor) might also trigger this exploit at will. This issue requires prompt injection from malicious data (web, image upload, source code) in order to exploit. In that case, it can send sensitive information to an attacker-controlled external server. Some additional bypasses not covered in the initial fix to this issue were discovered, see GHSA-43wj-mwcc-x93p. This issue is fixed in version 1.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 confidenceIn Cursor 1.6 and below, the Mermaid diagram renderer allows embedding external images. Through prompt injection (via malicious web content, image uploads, or source code), an attacker can cause Cursor to render Mermaid diagrams containing image tags pointing to attacker-controlled servers. When Cursor fetches these images, sensitive information from the chat context (potentially including code, API keys, or other displayed secrets) gets exfiltrated to the attacker's server via the HTTP request.
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< 1.7CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Cursor is installedLook for Cursor application in system locations: Windows typically in %LOCALAPPDATA%\Programs\cursor or C:\Program Files\Cursor; macOS in /Applications/Cursor.app; Linux in ~/.cursor or /opt/cursorAffected if Cursor application exists on the system
-
Determine installed Cursor versionOn Windows, check cursor.exe version via right-click > Properties > Details, or run: cursor --version in terminal if CLI available. On macOS, right-click Cursor.app > Get Info to see version, or run: /Applications/Cursor.app/Contents/MacOS/Cursor --versionAffected if Cannot determine version or version is below 1.7
-
Verify version against affected rangeCompare the found version number to the affected range: versions 1.6 and below are vulnerable; version 1.7 and later are patchedAffected if Installed version is 1.6 or lower (less than 1.7)
If Cursor is installed and the version is 1.6 or below, the environment is vulnerable to prompt injection via the Mermaid diagram renderer leading to potential data exfiltration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.7
Upgrade Cursor to version 1.7 or later to obtain the patched version. Additionally, treat code and content from untrusted sources with caution to avoid prompt injection vectors.
Cursor 1.7 or later
- Open Cursor application
- Navigate to the Help menu (or use keyboard shortcut)
- Select 'Check for Updates' to update to the latest version, or download Cursor version 1.7 or later from the official cursor.sh website
- Restart Cursor after the update completes
- Verify the version by checking Help > About Cursor - it should show version 1.7 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-61589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61589 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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