High 8.1Published Mar 27, 2026

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

Updated under an hour ago (Oct 26, 2026, 3:00 PM ET)

Does this affect you?

It affects mobile-next mobile-mcp and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for mobile-next mobile-mcp

Exploited in the last 30 days

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.

CVSS: 8.1 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Weakness (CWE): CWE-22, CWE-73
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: GitHub_M
NVD analysis: Analyzed
Record last updated: Mar 30, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

mobile-next mobile-mcp mobile_next:mobile_mcp (from the name)	before 0.0.49	CNA record
mobilenexthq mobile_mcp mobilenexthq:mobile_mcp	before 0.0.49	NVD

References

References

https://github.com/mobile-next/mobile-mcp/security/advisories/GHSA-3p2m-h2v6-g9mx	x-refsource-confirm, exploit, vendor-advisory
https://github.com/mobile-next/mobile-mcp/commit/f5e32295903128c1e71cf915ae6c0b76c7b0153b	x-refsource-misc, patch
https://github.com/mobile-next/mobile-mcp/releases/tag/0.0.49	x-refsource-misc, release-notes

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.