CVE-2026-33989: mobile-mcp · Path Traversal
Affects mobile-mcpSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 0.0.49 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.0.49
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade mobile-mcp to 0.0.49.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mobile-nextmobile-mcp | Affected
| Fixed in
|
AI-suggested
Upgrade the mobile-next mobile-mcp server to version 0.0.49 or later, where this vulnerability is fixed. Since this is not a cloud service, remediation depends on applying the official fix. Patch status is confirmed by the vendor's versioning information. No other mitigations are indicated by the vendor advisory.
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.