Command Injection in adb-mcp MCP Server

Exploitation

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

CVSS

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

EPSS

• CVE-2025-59834: 2.51% estimated exploitation activity in the next 30 days; percentile 84.82 (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.

Command Injection in adb-mcp MCP Server The MCP Server at https://github.com/srmorete/adb-mcp is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server is also published publicly to npm at www.npmjs.com/package/adb-mcp and allows users to install it. Vulnerable tool The MCP Server defines the function executeAdbCommand() which executes commands via string as a parameter and wraps the promise-based exec function. The MCP Server then exposes the tool inspectui which relies on Node.js child process API exec (through the function wrapper) to execute the Android debugging command (adb). Relying on exec is an unsafe and vulnerable API if concatenated with untrusted user input. Data flows from the tool definition here which takes in args.device and calls execPromise() in this definitino that uses exec in an insecure way. Vulnerable line of code:…

Published by the source

24 Sep 2025, 18:59 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-54j7-grvr-9xwg

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-54j7-grvr-9xwg

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

# Patch Next advisory brief: CVE-2025-59834

Advisory: Command Injection in adb-mcp MCP Server
IDs: CVE-2025-59834, GHSA-54j7-grvr-9xwg
Record: https://patchnext.com/advisories/cve-2025-59834 (revision 2, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm adb-mcp: affected <= 0.1.0

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on adb-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-54j7-grvr-9xwg (OSV record GHSA-54j7-grvr-9xwg lists affected ranges: npm adb-mcp >=0 <=0.1.0)
- Verified: https://github.com/advisories/GHSA-54j7-grvr-9xwg (GitHub-reviewed advisory GHSA-54j7-grvr-9xwg lists affected ranges: npm adb-mcp >=0 <=0.1.0)

Commands are suggestions: review each one before running it.