CVE-2026-32603 Overview
CVE-2026-32603 is a local denial of service vulnerability in the Sandboxie kernel driver. Sandboxie is an open source sandbox-based isolation software for Windows. The flaw affects versions 1.17.2 and earlier. An unprivileged process running inside a Standard Sandbox can send a malformed I/O Control (IOCTL) request to the \Device\SandboxieDriverApi driver. This triggers an immediate kernel crash, producing a Blue Screen of Death (BSOD). The issue impacts the Standard Sandbox configuration whether or not administrator privileges have been dropped. The Security Hardened Sandbox configuration is not affected. The maintainers fixed the issue in version 1.17.3.
Critical Impact
A low-privileged user inside a Standard Sandbox can crash the host Windows kernel, forcing a system reboot and disrupting availability for all users on the machine.
Affected Products
- Sandboxie versions 1.17.2 and earlier (Standard Sandbox configuration)
- Sandboxie kernel driver exposing \Device\SandboxieDriverApi
- Sandboxie deployments on Windows that have not migrated to the Security Hardened Sandbox
Discovery Timeline
- 2026-05-05 - CVE-2026-32603 published to NVD
- 2026-05-06 - Last updated in NVD database
- Sandboxie 1.17.3 - Security patch released by the Sandboxie-Plus project
Technical Details for CVE-2026-32603
Vulnerability Analysis
The Sandboxie kernel driver exposes the device object \Device\SandboxieDriverApi to user-mode processes for sandbox management and policy enforcement. Processes confined inside a Standard Sandbox retain the ability to issue IOCTL requests against this device. The driver fails to fully validate the structure or parameters of incoming control codes before acting on them. A specifically malformed IOCTL reaches a code path that dereferences invalid data inside kernel context, causing an immediate bugcheck. The defect is classified under Improper Input Validation [CWE-20]. Because the trigger originates from an unprivileged sandboxed process, the vulnerability undermines a core trust boundary the product is designed to enforce.
Root Cause
The root cause is missing or insufficient validation of user-supplied IOCTL input within the Sandboxie kernel driver. The Standard Sandbox does not block sandboxed processes from communicating with the driver interface, so untrusted callers can reach the vulnerable handler. The Security Hardened Sandbox restricts this attack surface, which is why that configuration is not affected.
Attack Vector
Exploitation requires local access. An attacker runs code inside a Standard Sandbox container, opens a handle to \Device\SandboxieDriverApi, and issues a crafted IOCTL using DeviceIoControl. The driver processes the malformed request and crashes the kernel. No elevation of privilege or remote network access is required. The impact is limited to availability — the system reboots, and no confidentiality or integrity loss has been reported. Refer to the GitHub Security Advisory GHSA-vvf8-cf4j-v8fv for vendor technical details.
Detection Methods for CVE-2026-32603
Indicators of Compromise
- Unexpected Windows bugcheck events (BugCheck 0x0000...) in the System event log shortly after sandboxed process activity.
- Kernel minidumps under C:\Windows\Minidump referencing the Sandboxie driver (SbieDrv.sys) in the faulting module stack.
- Sandboxed processes opening handles to \Device\SandboxieDriverApi followed immediately by a host reboot.
Detection Strategies
- Hunt for repeated unexpected reboots on endpoints running Sandboxie versions at or below 1.17.2.
- Correlate Sandboxie process telemetry with Windows Error Reporting (WER) and Event ID 1001 BugCheck records.
- Inspect crash dumps for stack frames inside the Sandboxie driver to confirm root cause attribution.
Monitoring Recommendations
- Inventory all hosts running Sandboxie and capture installed versions to identify unpatched systems.
- Alert on creation of new Standard Sandbox configurations in environments where Security Hardened Sandbox is the standard.
- Forward Windows kernel crash telemetry to a centralized SIEM or data lake for cross-host correlation.
How to Mitigate CVE-2026-32603
Immediate Actions Required
- Upgrade Sandboxie to version 1.17.3 or later on every affected Windows endpoint.
- Identify any Standard Sandbox boxes used by untrusted code or low-trust users and prioritize their remediation.
- Restrict local interactive logon on systems running unpatched Sandboxie until the update is applied.
Patch Information
The Sandboxie-Plus project addressed CVE-2026-32603 in the GitHub Release v1.17.3. The release adds validation to the IOCTL handler in the kernel driver, preventing malformed requests from reaching the vulnerable code path. Administrators should deploy the updated installer to all affected hosts and verify that the loaded SbieDrv.sys matches the patched version.
Workarounds
- Switch affected boxes to the Security Hardened Sandbox configuration, which is not vulnerable to this issue.
- Limit Sandboxie usage to trusted local users until patching is complete, since exploitation requires the ability to execute code inside a sandbox.
- Enable Windows automatic restart and crash dump collection so that any exploitation attempt is logged and recoverable.
# Verify installed Sandboxie version on Windows (PowerShell)
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' |
Where-Object { $_.DisplayName -like 'Sandboxie*' } |
Select-Object DisplayName, DisplayVersion, Publisher
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
