Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:HSummary
CVE-2026-33989 is a high-severity Path Traversal (CWE-22) vulnerability in Mobilenexthq Mobile Mcp. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as AI Agent Protocols and Integrations; in the Protocol-Specific Risks risk domain.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33989 is a path traversal vulnerability (CWE-22, CWE-73) affecting the `@mobilenext/mobile-mcp` server, part of Mobile Next, an MCP server used for mobile development and automation. In versions prior to 0.0.49, the `mobile_save_screenshot` and `mobile_start_screen_recording` tools insecurely handle the `saveTo` and `output` parameters, passing them directly to filesystem operations without validation. This allows arbitrary file writes outside the intended workspace. The vulnerability has a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H) and was published on 2026-03-27.
An unauthenticated attacker with network access to the server can exploit this vulnerability by tricking a user into invoking the affected tools with specially crafted `saveTo` or `output` parameters, such as those using directory traversal sequences like `../`. Successful exploitation enables writing files to arbitrary locations on the server's filesystem, potentially overwriting critical files and resulting in high integrity and availability impacts, though no confidentiality loss.
The GitHub security advisory (GHSA-3p2m-h2v6-g9mx), release notes for version 0.0.49, and fixing commit (f5e32295903128c1e71cf915ae6c0b76c7b0153b) confirm that upgrading to version 0.0.49 resolves the issue by adding proper validation to the parameters before filesystem operations. Security practitioners should prioritize updating affected instances and review logs for suspicious tool invocations.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16882
Vulnerability Data
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…
more
without validation, allowing an attacker to write files outside the intended workspace. Version 0.0.49 fixes the issue.
- CWE(s)
AI Security AnalysisAI
- AI Category
- AI Agent Protocols and Integrations
- Risk Domain
- Protocol-Specific Risks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: mcp
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices include input validation and path sanitization that eliminate this weakness.
Least-privilege file authorization directly limits damage from externally controlled paths.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.