Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Command Injection RCE in gemini-mcp-tool execAsync

IdentifiersCVE-2026-0755CWE-78· Improper Neutralization of Special…Also known aszdi_26_021zdi_can_27783

CVE-2026-0755 is a critical remote code execution vulnerability in gemini-mcp-tool. The flaw is in the implementation of the execAsync method, where a user-supplied string is not properly validated or sanitized before being used in a system call. This creates a command injection condition that allows a remote attacker to supply crafted input that is interpreted by the underlying operating system command execution path. Public reporting states the issue is network-exploitable, requires no authentication, and does not require user interaction. Successful exploitation results in arbitrary code execution in the context of the service account running gemini-mcp-tool.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated remote arbitrary code execution on affected gemini-mcp-tool installations with the privileges of the service account. Given the reported CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, impact can include full compromise of confidentiality, integrity, and availability available to that account, including execution of attacker-controlled commands, access to locally available data, modification of application state or files accessible to the service, and disruption of the service or host environment.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict interaction with gemini-mcp-tool to trusted users and trusted networks only, and avoid direct internet exposure. Do not allow untrusted input to reach functionality that invokes execAsync or related command-execution paths. Monitor hosts running the tool for suspicious process creation and unusual outbound network connections that may indicate exploitation. Where possible, run the service with a minimally privileged account and constrain filesystem and network access to reduce post-exploitation impact.

Remediation

Patch, then assume compromise.

Available supporting content indicates upgrading gemini-mcp-tool to version 1.1.6 or later. Advisory material also notes fixes including removal of unsafe command handling/quoting behavior and additional hardening around input handling. If authoritative vendor guidance is available in the canonical advisory, follow that guidance and deploy the fixed release across all affected installations.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AnyGemini-Mcp-Toolapplication
Gemini MCP ToolGemini-Mcp-Toolapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity10

Community discussion across Reddit, Mastodon, and other social sources.