# CVE-2026-33989: @mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools

> An attacker can write arbitrary files outside the intended workspace via path traversal in mobile screen capture tools.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-3p2m-h2v6-g9mx

## What is CVE-2026-33989?

CVE-2026-33989 is a high-severity path traversal vulnerability in mobile-next mobile-mcp, published on 27 Mar 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 version 0.0.49, the `@mobilenext/mobile-mcp` server contains a Path Traversal vulnerability in the `mobile_save_screenshot` and `mobile_start_screen_recording` tools. The `saveTo` and `output` parameters were passed directly to filesystem operations without validation, allowing an attacker to write files outside the intended workspace. Version 0.0.49 fixes the issue.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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.49 |
| `@mobilenext/mobile-mcp` | npm | All versions | 0.0.49 |

Products: Mobilenexthq Mobile Mcp.

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

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

## Is CVE-2026-33989 being exploited?

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

## Other vulnerabilities in mobile-next mobile-mcp

- [CVE-2026-35394](https://insights.sbomify.com/CVE-2026-35394/): Mobile Next has Arbitrary Android Intent Execution via mobile_open_url (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33989 is a high-severity path traversal vulnerability in mobile-next mobile-mcp, published on 27 Mar 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-33989 exists.

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

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-33989/ (Markdown: https://insights.sbomify.com/CVE-2026-33989/index.md)
```

## Sources

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

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