Unsafe Code Execution

BlenderMCP's download_polyhaven_asset tool fails to sanitize file paths derived from external API response keys, allowing an attacker who controls or intercepts that response to write files anywhere on disk, including dotfiles like .bashrc. This can be triggered either via a man-in-the-middle attack on the PolyHaven API or via a prompt injection that convinces the agent to fetch a malicious asset, ultimately leading to persistent code execution on the host running the MCP server.

Updated Jul 24, 2026 · CVSS 5.3

Researchers found a sandbox escape flaw in Anthropic's Claude Cowork that allows the AI agent (or something controlling it) to break out of its intended Linux VM isolation and read/write arbitrary files on the host Mac. This undermines the core security guarantee that the agent's actions are confined to the sandbox, exposing roughly 500,000 macOS users to potential host-level file access. This is a genuine isolation/architecture vulnerability rather than a prompt-injection-specific issue.

Updated Jul 24, 2026

An authenticated n8n user can craft a workflow expression that escapes the VM expression engine's sandbox by abusing array-element access to reach a host built-in object, then pollute its prototype in the main process. This causes a denial of service affecting the entire n8n instance, impacting both self-hosted and cloud deployments. n8n has patched the issue and users should upgrade immediately.

Updated Jul 23, 2026

LiteLLM's Skills feature fails to validate file paths when extracting uploaded ZIP archives, allowing an authenticated user with access to the Skills API to write files outside the intended directory. This 'zip-slip' style vulnerability could lead to arbitrary file write and potentially remote code execution depending on server configuration. The issue is fixed in version 1.83.7-stable.

Updated Jul 23, 2026

LiteLLM's proxy allowed custom Python code submitted through the Guardrails create/update API to run without the sandboxing applied on the test endpoint, enabling arbitrary code execution inside the proxy container. In deployments lacking a configured master key, any caller could be implicitly treated as an admin, making this reachable without real administrative access. This is a serious code-execution vulnerability in an AI infrastructure component, not merely a low-severity issue, given the potential for secret exposure and full proxy compromise.

Updated Jul 23, 2026

This is a duplicate advisory (superseded by GHSA-g3r5-9h93-4j2c) describing a time-of-check-to-time-of-use flaw in n8n's Git node clone operation. Authenticated attackers could swap a validated directory for a symlink to plant a malicious repository that n8n loads as a custom node on restart, achieving arbitrary code execution on the host. While the vulnerability itself is genuine and impactful, this specific advisory record carries no new information since it has been withdrawn in favor of the canonical GHSA entry.

Updated Jul 22, 2026

A time-of-check-to-time-of-use (TOCTOU) flaw in n8n's Git node lets an authenticated user swap a validated directory for a symlink right before the clone operation executes, planting a malicious repository into the custom node directory. Because n8n loads custom nodes as executable JavaScript on restart, this results in full remote code execution on the server. Both self-hosted and cloud n8n instances are affected wherever the Git node is usable by workflow authors.

Updated Jul 22, 2026

Langflow, a widely used visual builder for LLM/agent workflows, contains a vulnerability allowing remote attackers to execute arbitrary code by including functionality from an untrusted control sphere. This has been added to CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild, with a very short remediation window (3 days from add date to due date). Because Langflow is often used to orchestrate AI agents and connect them to tools and data sources, compromise of the platform can lead to full takeover of downstream agent pipelines and connected systems.

Updated Jul 22, 2026

MCP-for-Stata, an MCP server that lets AI agents drive Stata, fails to sanitize the log_file_name parameter before interpolating it into a Stata command string. An attacker (or a compromised upstream agent) can craft a malicious log_file_name to inject arbitrary Stata commands such as shell, python, or erase, achieving code execution on the host running the MCP server. The issue is patched in version 1.17.3.

Updated Jul 22, 2026

IBM Langflow, an open-source visual builder for AI agent/LLM workflows, contains a critical remote code execution flaw in its code validation API. Any authenticated user can submit Python code that is run directly via exec() with no sandboxing, granting them full control over the server process. Given a 9.9 CVSS score, this is a near-maximum severity issue requiring immediate patching or mitigation.

Updated Jul 19, 2026 · CVSS 9.9

IBM Langflow's disk caching component deserializes cached objects using Python's unsafe pickle.loads() without any validation or authentication. An attacker who can influence cache contents—via crafted workflow inputs, custom components, or API calls—can trigger arbitrary code execution with the privileges of the Langflow server, leading to full system compromise.

Updated Jul 19, 2026 · CVSS 9.9

ForgeCode, an AI pair-programming CLI, automatically parses and executes MCP server configurations from a repository's .mcp.json file without any user confirmation. A malicious or compromised repository can embed arbitrary OS commands in this file, achieving code execution with the developer's privileges the moment they run forge inside the cloned repo. This turns routine repository evaluation into a reliable initial-access vector for supply-chain attacks against developers.

Updated Jul 19, 2026 · CVSS 7.8

A vulnerability in IBM Langflow's Python Interpreter component allows an authenticated user to execute arbitrary commands with elevated privileges due to improper input validation. This affects Langflow OSS versions 1.0.0 through 1.10.1, and could allow an attacker with low-level access to escalate privileges and take control of the underlying system. Given the CVSS score of 8.8, this is a serious flaw that requires prompt patching.

Updated Jul 18, 2026 · CVSS 8.8

IBM Langflow OSS versions 1.0.0 through 1.10.1 expose a public flow build endpoint that allows unauthenticated remote code execution due to an incomplete security denylist. Attackers can construct flows using code-execution-capable agent components (OpenDsStarAgent, CodeActAgentSmolagents, CSVAgent) that are not blocked by the validation function, achieving arbitrary code execution without any authentication.

Updated Jul 18, 2026 · CVSS 8.1

IBM Langflow contains a vulnerability where its ToolGuard security policy fails to validate dynamically generated Python code fields, allowing attackers with flow creation privileges to inject and execute arbitrary code on the backend despite custom component restrictions being disabled. The flaw is worsened by an MCP tool that accepts attacker-controlled user IDs, enabling cross-tenant injection into other users' flows, and can require little to no authentication under common misconfigurations.

Updated Jul 18, 2026 · CVSS 9.9

IBM Langflow versions 1.0.0 through 1.10.0 contain a critical vulnerability chain allowing any unauthenticated network attacker to obtain superuser credentials and execute arbitrary code on the server. This affects default deployments of a widely used AI agent-building platform, giving attackers full control of the host and any connected agent workflows, data, or credentials.

Updated Jul 18, 2026 · CVSS 9.8

LiteLLM 1.18.10 allows any user who can submit MCP server configuration JSON to specify arbitrary OS commands and arguments that are executed unvalidated on the host. This gives an attacker remote code execution with the privileges of the LiteLLM process, a critical risk given the 9.8 CVSS score and the ease of exploitation.

Updated Jul 18, 2026 · CVSS 9.8

Agentic-Flow's MCP server tools passed user- and agent-supplied parameters (agent, task, name, language, agentdb) directly into shell commands via execSync() without sanitization, enabling arbitrary OS command execution. Any client, upstream agent, or automated caller able to invoke these MCP tools could achieve full remote code execution at the privilege level of the MCP server process. This is a critical, unauthenticated-adjacent injection flaw affecting core orchestration and swarm tooling.

Updated Jul 18, 2026 · CVSS 8.8

The Fay AI agent framework (version 4.3.1) exposes its MCP server management interface without adequate access control, allowing remote attackers to register a malicious MCP STDIO server with attacker-controlled commands. This results in full arbitrary command execution on the host running the Fay service, making it a critical, easily exploitable remote code execution vulnerability.

Updated Jul 17, 2026 · CVSS 9.8

Penpot's MCP server component exposed an unauthenticated HTTP endpoint bound to all network interfaces that allowed arbitrary JavaScript execution on the host. Any network-adjacent attacker could remotely execute code without credentials, making this a critical, easily exploitable vulnerability in an agent-tooling component.

Updated Jul 15, 2026 · CVSS 8.8