{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-64109 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64109 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64109 is a high-severity command injection vulnerability in cursor, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-64109 and fix it if it is affected.\n\nWhat it is: CVE-2025-64109 is a high-severity command injection vulnerability in cursor, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-64109 in the wild and no public exploit code.\n\nAffected product: cursor. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-64109/ (Markdown: https://insights.sbomify.com/CVE-2025-64109/index.md)","id":"CVE-2025-64109","markdown":"https://insights.sbomify.com/CVE-2025-64109/index.md","name":"CVE-2025-64109","record":{"aliases":[],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"AI code editor","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening a malicious repository with Cursor CLI, which auto-runs untrusted MCP server commands.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Cursor is a code editor built for programming with AI. In versions and below, a vulnerability in the Cursor CLI Beta allowed an attacker to achieve remote code execution through the MCP (Model Context Protocol) server mechanism by uploading a malicious MCP configuration in .cursor/mcp.json file in a GitHub repository. Once a victim clones the project and opens it using Cursor CLI, the command to run the malicious MCP server is immediately executed without any warning, leading to potential code execution as soon as the command runs. This issue is fixed in version 2025.09.17-25b418f.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cursor CLI Beta: Command Injection via Untrusted MCP Configuration","id":"CVE-2025-64109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cursor: Authentication Bypass Possible via New Cursorignore Write","id":"CVE-2025-64110"},"packages":[],"prev":{"headline":"Cursor's Sensitive File Modification can Lead to NTFS Path Quirks","id":"CVE-2025-64108"},"products":["cursor"],"published":"2025-11-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-07","vendors":["cursor"]},"summary":"Attackers can execute arbitrary code by tricking users into opening a malicious repository with Cursor CLI, which auto-runs untrusted MCP server commands.","url":"https://insights.sbomify.com/CVE-2025-64109/"}