{"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-35394 exists.","fix":"Upgrade @mobilenext/mobile-mcp to 0.0.50 or later.","what":"CVE-2026-35394 is a high-severity command injection vulnerability in mobile-next mobile-mcp, published on 6 Apr 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-35394 and fix it if it is affected.\n\nWhat it is: CVE-2026-35394 is a high-severity command injection vulnerability in mobile-next mobile-mcp, published on 6 Apr 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-35394 exists.\n\nAffected packages and fixed versions:\n- @mobilenext/mobile-mcp (npm): affected all versions; fixed in 0.0.50\n- @mobilenext/mobile-mcp (npm): affected all versions; fixed in 0.0.50\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-35394/ (Markdown: https://insights.sbomify.com/CVE-2026-35394/index.md)","id":"CVE-2026-35394","markdown":"https://insights.sbomify.com/CVE-2026-35394/index.md","name":"CVE-2026-35394","record":{"aliases":["GHSA-5qhv-x9j4-c3vm"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mobile MCP server","requires_auth":"none","summary":"Attackers can execute arbitrary Android intents, including calls and SMS, via the mobile_open_url tool in the Mobile Next MCP server.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mobile_mcp","vendor":"mobilenexthq"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-939","name":"Improper Authorization in Handler for Custom URL Scheme"}],"description":"Mobile Next is an MCP server for mobile development and automation. Prior to 0.0.50, the mobile_open_url tool in mobile-mcp passes user-supplied URLs directly to Android's intent system without any scheme validation, allowing execution of arbitrary Android intents, including USSD codes, phone calls, SMS messages, and content provider access. This vulnerability is fixed in 0.0.50.","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":"Mobile Next has Arbitrary Android Intent Execution via mobile_open_url","id":"CVE-2026-35394","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"WeGIA has a SQL Injection in DespachoDAO.php via id_memorando parameter","id":"CVE-2026-35395"},"packages":[{"ecosystem":"npm","fixed":["0.0.50"],"introduced":["0"],"last_affected":[],"package":"@mobilenext/mobile-mcp","purl":null,"source":"GHSA-5qhv-x9j4-c3vm"},{"ecosystem":"npm","fixed":["0.0.50"],"introduced":["0"],"last_affected":[],"package":"@mobilenext/mobile-mcp","purl":"pkg:npm/%40mobilenext/mobile-mcp","source":"GHSA-5qhv-x9j4-c3vm"}],"prev":{"headline":"Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in goshs POST multipart upload","id":"CVE-2026-35393"},"products":["mobile-mcp"],"published":"2026-04-06","related":[{"cvss_score":8.1,"headline":"@mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools","id":"CVE-2026-33989","kev_date_added":null,"published":"2026-03-27"}],"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-04-07","vendors":["mobile-next"]},"summary":"Attackers can execute arbitrary Android intents, including calls and SMS, via the mobile_open_url tool in the Mobile Next MCP server.","url":"https://insights.sbomify.com/CVE-2026-35394/"}