{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64106 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64106 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-64106 and fix it if it is affected.\n\nWhat it is: CVE-2025-64106 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-64106 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-64106/ (Markdown: https://insights.sbomify.com/CVE-2025-64106/index.md)","id":"CVE-2025-64106","markdown":"https://insights.sbomify.com/CVE-2025-64106/index.md","name":"CVE-2025-64106","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 commands by tricking users into accepting malicious deep-links that bypass security warnings in Cursor.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cursor","vendor":"anysphere"}],"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 1.7.28 and below, an input validation flaw in Cursor's MCP server installation enables specially crafted deep-links to bypass the standard security warnings and conceal executed commands from users if they choose to accept the server. If an attacker is able to convince a victim to navigate to a malicious deeplink, the victim will not see the correct speedbump modal, and if they choose to accept, will execute commands specified by the attackers deeplink.","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: Speedbump Modal Bypass in MCP Server Deep-Link","id":"CVE-2025-64106","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 is Vulnerable to Path Manipulation Using Backslashes on Windows","id":"CVE-2025-64107"},"packages":[],"prev":{"headline":"FOSSBilling: IDOR Vulnerability in Support Ticket Creation","id":"CVE-2025-64105"},"products":["cursor"],"published":"2025-11-04","related":[{"cvss_score":9.3,"headline":"Cursor Desktop sandbox escape via agent-controlled working directory","id":"CVE-2026-50548","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":9.3,"headline":"Cursor Desktop sandbox escape via symlink and failed path canonicalization","id":"CVE-2026-50549","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":8.8,"headline":"Cursor is Vulnerable to Path Manipulation Using Backslashes on Windows","id":"CVE-2025-64107","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":8.8,"headline":"Cursor's Sensitive File Modification can Lead to NTFS Path Quirks","id":"CVE-2025-64108","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":8.8,"headline":"Cursor CLI's Cursor Agent MCP OAuth2 Communication is Vulnerable to Remote Code Execution","id":"CVE-2025-61591","kev_date_added":null,"published":"2025-10-03"},{"cvss_score":8.8,"headline":"Cursor CLI: Arbitrary Code Execution Possible through Permissive CLI Config","id":"CVE-2025-61592","kev_date_added":null,"published":"2025-10-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-05","vendors":["cursor"]},"summary":"Attackers can execute arbitrary commands by tricking users into accepting malicious deep-links that bypass security warnings in Cursor.","url":"https://insights.sbomify.com/CVE-2025-64106/"}