{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50548 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50548 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50548 is a critical path traversal vulnerability in cursor, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50548 and fix it if it is affected.\n\nWhat it is: CVE-2026-50548 is a critical path traversal vulnerability in cursor, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50548 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-2026-50548/ (Markdown: https://insights.sbomify.com/CVE-2026-50548/index.md)","id":"CVE-2026-50548","markdown":"https://insights.sbomify.com/CVE-2026-50548/index.md","name":"CVE-2026-50548","record":{"aliases":[],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"AI code editor","requires_auth":"none","summary":"A malicious AI agent can escape the sandbox by manipulating the working directory to write files outside the workspace, enabling remote code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cursor","vendor":"anysphere"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Cursor is a code editor built for programming with AI. Prior to 3.0, Cursor runs agent terminal commands in a sandbox by default, and the sandbox grants write access to the command's working directory. A flaw was identified in how the agent could modify the working_directory parameter, which could cause the sandbox to include writable paths outside the intended workspace. A malicious agent could set working_directory to a sensitive location and write arbitrary files outside the workspace under the user's privileges. This enables non-sandboxed Remote Code Execution — for example by overwriting the cursorsandbox helper so later commands run unsandboxed — with no user interaction beyond a benign prompt. This vulnerability is fixed in 3.0.","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 Desktop sandbox escape via agent-controlled working directory","id":"CVE-2026-50548","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cursor Desktop sandbox escape via symlink and failed path canonicalization","id":"CVE-2026-50549"},"packages":[],"prev":{"headline":"InvoicePlane permits local file inclusion through the e-invoice XML configuration identifier","id":"CVE-2026-50547"},"products":["cursor"],"published":"2026-06-25","related":[{"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: Speedbump Modal Bypass in MCP Server Deep-Link","id":"CVE-2025-64106","kev_date_added":null,"published":"2025-11-04"},{"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["cursor"]},"summary":"A malicious AI agent can escape the sandbox by manipulating the working directory to write files outside the workspace, enabling remote code execution.","url":"https://insights.sbomify.com/CVE-2026-50548/"}