Summaryinfo

A vulnerability was found in mobile-next mobile-mcp up to 0.0.48. It has been classified as critical. This affects the function mobile_save_screenshot/mobile_start_screen_recording of the component Fileystem Operation Handler. The manipulation of the argument saveTo/output leads to path traversal. This vulnerability is referenced as CVE-2026-33989. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in mobile-next mobile-mcp up to 0.0.48 and classified as critical. This issue affects the function mobile_save_screenshot/mobile_start_screen_recording of the component Fileystem Operation Handler. The manipulation of the argument saveTo/output with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-33989 since 03/24/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 0.0.49 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch f5e32295903128c1e71cf915ae6c0b76c7b0153b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• mobile-next

Name

• mobile-mcp

Version

• 0.0.1
• 0.0.2
• 0.0.3
• 0.0.4
• 0.0.5
• 0.0.6
• 0.0.7
• 0.0.8
• 0.0.9
• 0.0.10
• 0.0.11
• 0.0.12
• 0.0.13
• 0.0.14
• 0.0.15
• 0.0.16
• 0.0.17
• 0.0.18
• 0.0.19
• 0.0.20
• 0.0.21
• 0.0.22
• 0.0.23
• 0.0.24
• 0.0.25
• 0.0.26
• 0.0.27
• 0.0.28
• 0.0.29
• 0.0.30
• 0.0.31
• 0.0.32
• 0.0.33
• 0.0.34
• 0.0.35
• 0.0.36
• 0.0.37
• 0.0.38
• 0.0.39
• 0.0.40
• 0.0.41
• 0.0.42
• 0.0.43
• 0.0.44
• 0.0.45
• 0.0.46
• 0.0.47
• 0.0.48

License

• open-source

Website

• Product: https://github.com/mobile-next/mobile-mcp/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion