Code execution via unprotected workspace settings write
Published Oct 3, 2025 · Updated Oct 3, 2025
Code injection in Anysphere Cursor before 1.7 allows attackers to execute code through a modified Visual Studio Code workspace file. A hijacked chat context can prompt the Cursor Agent to write attacker-controlled settings into an existing or automatically maintained .code-workspace file that was not treated as sensitive. Exploitation requires control of chat context, such as through a compromised MCP server, and runs code on the victim host without approval.
Summary
What happened
Code injection in Anysphere Cursor before 1.7 allows attackers to execute code through a modified Visual Studio Code workspace file. A hijacked chat context can prompt the Cursor Agent to write attacker-controlled settings into an existing or automatically maintained .code-workspace file that was not treated as sensitive. Exploitation requires control of chat context, such as through a compromised MCP server, and runs code on the victim host without approval.
The record
- CVE
- CVE-2025-61590
- Published
- Oct 3, 2025
- Updated
- Oct 3, 2025
- Vendor
- Anysphere
- Product
- Cursor
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 3, 2025CVE publishedPublication date reported by the CVE source.
- Oct 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo