External risk intelligence

Sandboxie SYSTEM Heap Overflow Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2025-64721

Sandboxie is host-based isolation software that runs locally on an endpoint. The vulnerability requires a process to already be running within the sandbox to interact with the local SYSTEM-level service. It is not an internet-facing service or network gateway, and exposure is limited to the local system environment.

Integer Overflow

Sandboxie Plus Sandboxie

1.14.0 to before 1.16.7

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This CVE involves a critical vulnerability in Sandboxie software that allows malicious code to execute with system-level privileges. This could enable attackers to gain complete control over an affected host system if they can execute code within a sandboxed environment. The main concern is confirming relevance and exposure to this type of software.

  • Code execution bypasses sandbox protections.
  • Critical risk if host system is compromised.
  • Confirm if this software is in use.

Attack Path

How an attacker could exploit the issue

An attacker could leverage a vulnerability within Sandboxie's SYSTEM-level service to execute arbitrary code. This begins with a process already running inside a sandbox, which then interacts with the vulnerable service. By manipulating data length, the attacker can cause a heap overflow, allowing them to run code with the highest system privileges, effectively compromising the entire host.

  • Vulnerable SYSTEM-level service exposure.
  • Heap overflow due to unchecked data length.
  • Arbitrary code execution as SYSTEM.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow a process running inside a Sandboxie sandbox to execute arbitrary code with SYSTEM privileges on the host. This occurs when a sandboxed process interacts with a vulnerable SYSTEM-level service by sending a crafted length value that triggers a heap overflow, enabling the attacker's data to overwrite adjacent memory.

  • System code execution as SYSTEM.
  • Heap overflow via crafted length.
  • Full host compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world action for this critical vulnerability likely falls to the endpoint security teams and system owners responsible for managing user workstations and any servers utilizing Sandboxie for isolation. The first practical move is to identify all systems running the affected software, confirm if these systems are actively used for business-critical functions, and then locate the specific teams or individuals accountable for these assets to initiate a coordinated remediation plan based on the assessed risk.

  • Own the issue: Endpoint security and system owners.
  • Verify first: Identify all affected systems and criticality.
  • Action: Plan and coordinate remediation efforts.

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 Sandboxie and how is it used?

Sandboxie is software designed to provide a secure, isolated environment on Windows operating systems. By running applications inside a sandbox, users create a restricted space that separates these programs from the underlying host system. It is commonly used to safely test untrusted software or browse the web, ensuring that changes made by sandboxed applications do not permanently impact the host operating system.

What kind of vulnerability is CVE-2025-64721?

This vulnerability is classified as an integer overflow (CWE-190) that leads to a heap overflow. In plain terms, the software fails to properly check the size of incoming data before allocating memory for it. An attacker can provide an extremely large value that wraps around, resulting in a buffer that is too small for the data being copied. This error allows the process to overwrite nearby memory, which can be exploited to run arbitrary code.

How is this Sandboxie vulnerability triggered?

The flaw is triggered when a process already running inside the sandbox interacts with the SbieSvc.exe service. By sending a specifically crafted, invalid length value to the service's memory-handling function, an attacker forces a memory management error. Importantly, simply having the software installed does not trigger the bug; it requires a malicious or compromised process to be actively running within the isolated environment to initiate the interaction.

Is my system at risk according to Halo Surface Signal?

According to Halo Surface Signal, this vulnerability is very unlikely to be exposed to the internet. Because Sandboxie is host-based isolation software that operates locally on an endpoint, the vulnerability is confined to your local system environment. It is not a network gateway or public-facing service, meaning the risk is limited to attackers who have already established a foothold by running a process inside one of your sandboxes.

How should I respond if I use Sandboxie?

The first step is to identify all endpoints in your environment where Sandboxie is installed. Once you have a clear inventory, prioritize systems based on their use and sensitivity. Since the vulnerability is fixed in version 1.16.7, plan an orderly update process for all affected instances. Coordinate with your endpoint security or system administration teams to ensure the patch is applied across your fleet to restore the integrity of the sandbox isolation.

References