Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

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

CVE-2026-35394GHSA-5qhv-x9j4-c3vm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@mobilenext/mobile-mcp 0.0.50), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H
EPSS
  • CVE-2026-35394: 0.40% estimated exploitation activity in the next 30 days; percentile 34.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The mobileopenurl 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 -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-5qhv-x9j4-c3vm

  2. Revision 1 · created ·

    Published from osv record GHSA-5qhv-x9j4-c3vm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35394

Advisory: @mobilenext/mobile-mcp: Arbitrary Android Intent Execution via mobile_open_url
IDs: CVE-2026-35394, GHSA-5qhv-x9j4-c3vm
Record: https://patchnext.com/advisories/cve-2026-35394 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @mobilenext/mobile-mcp 0.0.50. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @mobilenext/mobile-mcp: affected < 0.0.50; fixed in 0.0.50

## Suggested inspection (read-only)
- `npm ls @mobilenext/mobile-mcp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @mobilenext/mobile-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5qhv-x9j4-c3vm (OSV record GHSA-5qhv-x9j4-c3vm lists affected ranges: npm @mobilenext/mobile-mcp >=0 <0.0.50 (fixed))
- Verified: https://github.com/advisories/GHSA-5qhv-x9j4-c3vm (GitHub-reviewed advisory GHSA-5qhv-x9j4-c3vm lists affected ranges: npm @mobilenext/mobile-mcp >=0 <0.0.50)

Commands are suggestions: review each one before running it.

Loading voting…