Skip to content

← Public intelligence

npm package

@mobilenext/mobile-mcp

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.3npmAmendedPublished

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

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

    Affected
    • npm @mobilenext/mobile-mcp < 0.0.50
    Fixed in
    0.0.50· Vendor fix available
    Issue
    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 -…

    Recommended action: Upgrade to 0.0.50 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.1npmAmendedPublished

    @mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools

    CVE-2026-33989 · GHSA-3p2m-h2v6-g9mx

    Affected
    • npm @mobilenext/mobile-mcp < 0.0.49
    Fixed in
    0.0.49· Vendor fix available
    Issue
    The @mobilenext/mobile-mcp server contains a Path Traversal vulnerability in the mobilesavescreenshot and mobilestartscreenrecording tools. The saveTo and output parameters were passed directly to filesystem operations without validation, allowing an attacker to write files outside the intended workspace. Details File: src/server.ts (lines 584-592) Root Cause The saveTo parameter is passed directly to fs.writeFileSync() without any validation. The codebase has validation functions for other parameters (validatePackageName, validateLocale in src/utils.ts) but no path validation function exists. Additional Affected Tool File: src/server.ts (lines 597-620) The mobilestartscreenrecording tool has the same vulnerability in its output parameter. PoC Impact A Prompt Injection attack from a malicious website or document could trick the AI into overwriting sensitive host files (e.g., ~/.bashrc, ~/.ssh/authorizedkeys, or .config files) leading to a broken shell.

    Recommended action: Upgrade to 0.0.49 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →