# CVE-2026-35394: Mobile Next has Arbitrary Android Intent Execution via mobile_open_url

> Attackers can execute arbitrary Android intents, including calls and SMS, via the mobile_open_url tool in the Mobile Next MCP server.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-5qhv-x9j4-c3vm

## What is CVE-2026-35394?

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.

### Official 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.

Weakness: CWE-939 (Improper Authorization in Handler for Custom URL Scheme)

## Which versions are affected by CVE-2026-35394?

2 open source packages ship an affected version, including @mobilenext/mobile-mcp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@mobilenext/mobile-mcp` | npm | All versions | 0.0.50 |
| `@mobilenext/mobile-mcp` | npm | All versions | 0.0.50 |

Products: Mobilenexthq Mobile Mcp.

## How do I fix CVE-2026-35394?

Upgrade @mobilenext/mobile-mcp to 0.0.50 or later.

## Is CVE-2026-35394 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35394 exists.

## Other vulnerabilities in mobile-next mobile-mcp

- [CVE-2026-33989](https://insights.sbomify.com/CVE-2026-33989/): @mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35394 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35394 exists.

Affected packages and fixed versions:
- @mobilenext/mobile-mcp (npm): affected all versions; fixed in 0.0.50
- @mobilenext/mobile-mcp (npm): affected all versions; fixed in 0.0.50

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35394/ (Markdown: https://insights.sbomify.com/CVE-2026-35394/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35394
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35394
- OSV: https://osv.dev/vulnerability/CVE-2026-35394

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35394/
Summaries are generated and may contain mistakes; the official description above is the record.