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

Remote Command Execution in GPT Researcher via malicious MCP STDIO configuration

IdentifiersCVE-2025-65720CWE-78

CVE-2025-65720 is a remote command execution vulnerability affecting GPT Researcher. Based on the provided reporting, the issue is tied to unsafe handling of Model Context Protocol (MCP) STDIO server configuration, where attacker-controlled command and argument values can be executed on the host running GPT Researcher. The supplied context states that all versions are affected and that exploitation can be triggered when a victim accesses an attacker-controlled crafted HTML page, which then causes command execution and can spawn a reverse shell on the machine running GPT Researcher locally. The vulnerability is described as part of a broader class of MCP STDIO command-injection issues in which untrusted configuration or content influences subprocess execution without sufficient sanitization or trust separation.

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 results in arbitrary operating system command execution on the machine running GPT Researcher, with the privileges of the GPT Researcher process. The provided context specifically notes reverse-shell execution as a demonstrated outcome. This can lead to full host compromise, theft of local data and credentials, installation of persistence mechanisms, lateral movement, and abuse of any network, cloud, or SaaS access available from the compromised system.

Mitigation

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

Until an official patch is available, reduce exposure by disabling or avoiding MCP STDIO-based functionality if possible, treating all external MCP configuration and untrusted content as hostile, and preventing untrusted web content from interacting with local GPT Researcher instances. Run GPT Researcher with least privilege, isolate it in a sandboxed/containerized environment, restrict outbound network access to limit reverse-shell behavior, and avoid exposing related services or interfaces unnecessarily. Monitoring for unexpected child-process creation and suspicious command execution from the GPT Researcher host is also advisable.

Remediation

Patch, then assume compromise.

The provided content states that GPT Researcher had no patch available at the time of reporting. Specific vendor remediation details are therefore currently not available. If a vendor fix becomes available, upgrading to the patched release should be the primary remediation.
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.

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 activity

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