External risk intelligence

FrontMCP Sandbox Escape Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-67531

The framework is designed to provide Model Context Protocol services, which are inherently intended to be network-accessible. The vulnerability affects servers configured in public mode by default, allowing unauthenticated remote access to the framework's functions, directly exposing the service endpoint to the internet.

Code Injection

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in the FrontMCP framework allows unauthenticated attackers to execute arbitrary code on the server. This could expose sensitive information such as API secrets and credentials. The issue arises from how the framework handles sandboxed code execution and Zod schema instances, allowing a script to bypass security measures and gain remote code execution.

  • Code execution vulnerability in a server framework.
  • Potential exposure of sensitive server secrets.
  • Confirm relevance and scope of this framework.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by interacting with the FrontMCP framework, which by default allows unauthenticated access. By sending a crafted request to the `codecall:execute` tool, an attacker can manipulate the framework to expose Zod schema instances. This allows the attacker to access the `_zod.constr.constructor` property, ultimately leading to the execution of arbitrary code on the server. The vulnerability can be triggered by a single tool call, and in default configurations, this can be achieved without any authentication, potentially exposing sensitive server information.

  • Entry condition: Public server mode, unauthenticated access.
  • Trigger point: Call the `codecall:execute` tool.
  • Resulting risk: Arbitrary code execution, server secrets exposed.

Live Threat

Current exploitation, exposure, and threat context

The FrontMCP framework's sandboxed code execution feature can be exploited to gain remote code execution on the server. This occurs when a script accesses live Zod schema instances through the `getTool()` function, allowing it to reach the host's `Function` constructor and execute arbitrary code. This could expose sensitive server-side information such as OAuth client secrets, JWT secrets, session keys, database credentials, and cloud instance metadata.

  • Sensitive server secrets and credentials.
  • Arbitrary code execution via tool access.
  • Complete server compromise and data theft.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Platform or Application Development team is likely responsible for managing the FrontMCP framework. The first practical step is to inventory all instances of this framework, determine their accessibility and business criticality, and identify the accountable owner for each. Subsequently, a remediation plan can be developed based on the assessed risk.

  • Identify accountable platform owners.
  • Verify exposure and critical systems.
  • Plan and coordinate secure updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is FrontMCP?

FrontMCP is a framework built with TypeScript designed to support the Model Context Protocol. It acts as a bridge that allows AI models or agents to interact with tools and local environments. Developers use it to create service endpoints that expose functions—such as code execution or data retrieval—to language models, enabling these models to perform tasks on a host server.

What does CWE-94 mean in the context of CVE-2026-67531?

CWE-94 refers to Improper Control of Generation of Code, commonly known as Code Injection. In this CVE, the vulnerability allows a script running inside the framework's sandbox to break out and access the underlying host system. By exploiting how the software handles specific object instances, a script can reach the host's internal functionality and run arbitrary commands as the server process, effectively bypassing intended security boundaries.

How can an attacker trigger this vulnerability?

An attacker triggers the bug by sending a specific request to the codecall:execute tool. Because the framework's security membrane fails to protect host objects during this process, the attacker can leverage the environment to execute malicious code. Note that simply interacting with a server running FrontMCP is the primary requirement; however, code that does not utilize the codecall:execute tool or does not interact with protected Zod schema instances would not trigger this specific path.

Is my server at risk?

Your risk depends on how the server is configured. According to Halo Surface Signal, this framework is designed to be network-accessible, and because default installations often run in a public mode without authentication, the service may be reachable from the internet. If your FrontMCP instance is configured to be public or handles untrusted inputs, it is significantly more likely to be reachable by an attacker compared to a server restricted to a private, authenticated network.

What should I do first to address this?

Your first step is to perform an inventory of all systems running the FrontMCP framework to determine which are active and their current version. Since this vulnerability is resolved in version 1.5.7, you should prioritize updating any instances found below that version. Additionally, evaluate the access controls on your servers to ensure they are not inadvertently exposed in public mode while you coordinate these updates.

References