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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

EPSS

• CVE-2026-33989: 0.50% estimated exploitation activity in the next 30 days; percentile 42.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The @mobilenext/mobile-mcp server contains a Path Traversal vulnerability in the mobilesavescreenshot and mobilestartscreenrecording tools. The saveTo and output parameters were passed directly to filesystem operations without validation, allowing an attacker to write files outside the intended workspace. Details File: src/server.ts (lines 584-592) Root Cause The saveTo parameter is passed directly to fs.writeFileSync() without any validation. The codebase has validation functions for other parameters (validatePackageName, validateLocale in src/utils.ts) but no path validation function exists. Additional Affected Tool File: src/server.ts (lines 597-620) The mobilestartscreenrecording tool has the same vulnerability in its output parameter. PoC Impact A Prompt Injection attack from a malicious website or document could trick the AI into overwriting sensitive host files (e.g., ~/.bashrc, ~/.ssh/authorizedkeys, or .config files) leading to a broken shell.

Published by the source

27 Mar 2026, 19:13 UTC

Last modified by the source

30 Mar 2026, 20:34 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3p2m-h2v6-g9mx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3p2m-h2v6-g9mx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33989

Advisory: @mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools
IDs: CVE-2026-33989, GHSA-3p2m-h2v6-g9mx
Record: https://patchnext.com/advisories/cve-2026-33989 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @mobilenext/mobile-mcp 0.0.49. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @mobilenext/mobile-mcp: affected < 0.0.49; fixed in 0.0.49

## Suggested inspection (read-only)
- `npm ls @mobilenext/mobile-mcp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @mobilenext/mobile-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3p2m-h2v6-g9mx (OSV record GHSA-3p2m-h2v6-g9mx lists affected ranges: npm @mobilenext/mobile-mcp >=0 <0.0.49 (fixed))
- Verified: https://github.com/advisories/GHSA-3p2m-h2v6-g9mx (GitHub-reviewed advisory GHSA-3p2m-h2v6-g9mx lists affected ranges: npm @mobilenext/mobile-mcp >=0 <0.0.49)

Commands are suggestions: review each one before running it.