{"answers":{"affected":"2 open source packages ship an affected version, including @mobilenext/mobile-mcp. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33989 exists.","fix":"Upgrade @mobilenext/mobile-mcp to 0.0.49 or later.","what":"CVE-2026-33989 is a high-severity path traversal vulnerability in mobile-next mobile-mcp, published on 27 Mar 2026. 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-2026-33989 and fix it if it is affected.\n\nWhat it is: CVE-2026-33989 is a high-severity path traversal vulnerability in mobile-next mobile-mcp, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33989 exists.\n\nAffected packages and fixed versions:\n- @mobilenext/mobile-mcp (npm): affected all versions; fixed in 0.0.49\n- @mobilenext/mobile-mcp (npm): affected all versions; fixed in 0.0.49\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-33989/ (Markdown: https://insights.sbomify.com/CVE-2026-33989/index.md)","id":"CVE-2026-33989","markdown":"https://insights.sbomify.com/CVE-2026-33989/index.md","name":"CVE-2026-33989","record":{"aliases":["GHSA-3p2m-h2v6-g9mx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Mobile MCP server","requires_auth":"none","summary":"An attacker can write arbitrary files outside the intended workspace via path traversal in mobile screen capture tools.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mobile_mcp","vendor":"mobilenexthq"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Mobile Next is an MCP server for mobile development and automation. Prior to version 0.0.49, the `@mobilenext/mobile-mcp` server contains a Path Traversal vulnerability in the `mobile_save_screenshot` and `mobile_start_screen_recording` tools. The `saveTo` and `output` parameters were passed directly to filesystem operations without validation, allowing an attacker to write files outside the intended workspace. Version 0.0.49 fixes the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"@mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools","id":"CVE-2026-33989","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Docker Model Runner OCI Registry Client Vulnerable to Server-Side Request Forgery (SSRF)","id":"CVE-2026-33990"},"packages":[{"ecosystem":"npm","fixed":["0.0.49"],"introduced":["0"],"last_affected":[],"package":"@mobilenext/mobile-mcp","purl":null,"source":"GHSA-3p2m-h2v6-g9mx"},{"ecosystem":"npm","fixed":["0.0.49"],"introduced":["0"],"last_affected":[],"package":"@mobilenext/mobile-mcp","purl":"pkg:npm/%40mobilenext/mobile-mcp","source":"GHSA-3p2m-h2v6-g9mx"}],"prev":{"headline":"FreeRDP: Persistent Cache bmpSize Desync - Heap OOB Write","id":"CVE-2026-33987"},"products":["mobile-mcp"],"published":"2026-03-27","related":[{"cvss_score":8.3,"headline":"Mobile Next has Arbitrary Android Intent Execution via mobile_open_url","id":"CVE-2026-35394","kev_date_added":null,"published":"2026-04-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["mobile-next"]},"summary":"An attacker can write arbitrary files outside the intended workspace via path traversal in mobile screen capture tools.","url":"https://insights.sbomify.com/CVE-2026-33989/"}