CVE-2025-32018: Arbitrary file write from Cursor Agent through a prompt injection from malicious @Docs
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-32018?
CVE-2025-32018 is classified as a moderate severity vulnerability due to its ability to allow unauthorized file path modifications under specific conditions.
How do I fix CVE-2025-32018?
To mitigate CVE-2025-32018, users should update Cursor to a version beyond 0.48.6 to eliminate the regression causing the vulnerability.
Which versions of Cursor are affected by CVE-2025-32018?
CVE-2025-32018 affects Cursor versions 0.45.0 through 0.48.6.
What are the potential impacts of CVE-2025-32018?
The potential impact of CVE-2025-32018 includes unauthorized modifications to file paths made by the Cursor Agent.
Who is the vendor responsible for CVE-2025-32018?
The vendor responsible for CVE-2025-32018 is Cursor, which develops the Cursor code editor.