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

High 8.1 Published Updated

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

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

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, CWE-22

Which versions are affected by CVE-2026-33989?

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

PackageAffectedFixed in
@mobilenext/mobile-mcp npmAll versions0.0.49
@mobilenext/mobile-mcp npmAll versions0.0.49

Products include Mobilenexthq Mobile Mcp.

How do I fix CVE-2026-33989?

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

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-33989 being exploited?

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

Sources

Also known as GHSA-3p2m-h2v6-g9mx.

Is CVE-2026-33989 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free