CVE-2026-35394

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.

Details

The vulnerable code passes URLs directly to adb shell am start -a android.intent.action.VIEW -d <url> without checking the URL scheme. This can enable malicious schemes such as tel:, sms:, mailto:, content://, and market:// to be executed.

Since MCP servers are designed to be operated by AI agents, which are vulnerable to prompt injection attacks, a malicious document or website could inject instructions that cause the AI to execute dangerous intents on a connected mobile device.

Proof of Concept

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"mobile_open_url","arguments":{"device":"<id>","url":"tel:*#06#"}}}

Result: IMEI displayed on device.

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"mobile_open_url","arguments":{"device":"<id>","url":"sms:1234567890?body=HACKED"}}}

Result: SMS app opens with a pre-filled message.

An attacker via prompt injection can:

• Execute USSD codes (e.g., tel:*#06# to display IMEI - confirmed on Pixel 7a, behavior varies by device; or device-specific factory reset codes)
• Initiate phone calls to premium rate numbers
• Draft SMS messages with attacker-controlled content
• Access content providers (contacts, SMS, call logs)
• Open app installation prompts

CVE-2026-35394 has a CVSS score of 8.3 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.50); upgrading removes the vulnerable code path.

Kodem intelligence

Upgrade to version 0.0.50 or later, which restricts mobile_open_url to http:// and https:// schemes by default. Users who require other URL schemes can opt in by setting MOBILEMCP_ALLOW_UNSAFE_URLS=1.

1. What is CVE-2026-35394? CVE-2026-35394 is a high-severity security vulnerability in @mobilenext/mobile-mcp (npm), affecting versions < 0.0.50. It is fixed in 0.0.50.
2. How severe is CVE-2026-35394? CVE-2026-35394 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @mobilenext/mobile-mcp are affected by CVE-2026-35394? @mobilenext/mobile-mcp (npm) versions < 0.0.50 is affected.
4. Is there a fix for CVE-2026-35394? Yes. CVE-2026-35394 is fixed in 0.0.50. Upgrade to this version or later.
5. Is CVE-2026-35394 exploitable, and should I be worried? Whether CVE-2026-35394 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-35394 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-35394? Upgrade @mobilenext/mobile-mcp to 0.0.50 or later.