Skip to content

@mobilenext/mobile-mcp: Arbitrary Android Intent Execution via mobile_open_url

High severity GitHub Reviewed Published Apr 2, 2026 in mobile-next/mobile-mcp

Package

npm @mobilenext/mobile-mcp (npm)

Affected versions

< 0.0.50

Patched versions

0.0.50

Description

Summary

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.

Impact

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

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.

Remediation

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.

References

@gmegidish gmegidish published to mobile-next/mobile-mcp Apr 2, 2026
Published to the GitHub Advisory Database Apr 4, 2026
Reviewed Apr 4, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H

EPSS score

Weaknesses

Improper Authorization in Handler for Custom URL Scheme

The product uses a handler for a custom URL scheme, but it does not properly restrict which actors can invoke the handler using the scheme. Learn more on MITRE.

CVE ID

CVE-2026-35394

GHSA ID

GHSA-5qhv-x9j4-c3vm

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.