Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-34596

CVE-2026-34596: Sandboxie-Plus Race Condition Vulnerability

CVE-2026-34596 is a Time-of-Check-to-Time-of-Use race condition flaw in Sandboxie-Plus that allows privilege escalation to SYSTEM during addon installation. This post covers technical details, affected versions, and fixes.

Published:

CVE-2026-34596 Overview

CVE-2026-34596 is a Time-of-Check-to-Time-of-Use (TOCTOU) race condition [CWE-367] in Sandboxie-Plus, an open source sandbox-based isolation tool for Windows. Versions 1.17.2 and earlier stage addon installation files in the user-writable %TEMP%\sandboxie-updater directory while UpdUtil.exe runs as SYSTEM under SbieSvc. An unprivileged local attacker can swap files.cab between hash verification and extraction, gaining SYSTEM execution without a User Account Control (UAC) prompt. The maintainers fixed the issue in version 1.17.3.

Critical Impact

A local low-privileged user can win a race against the addon installer to execute arbitrary code as SYSTEM, bypassing UAC entirely.

Affected Products

  • Sandboxie-Plus versions 1.17.2 and earlier
  • UpdUtil.exe addon installation component
  • SbieSvc service handling SandMan addon installs

Discovery Timeline

  • 2026-05-05 - CVE-2026-34596 published to NVD
  • 2026-05-06 - Last updated in NVD database

Technical Details for CVE-2026-34596

Vulnerability Analysis

The vulnerability resides in the addon installation flow exposed through the SandMan user interface. When a user requests an addon, SbieSvc spawns UpdUtil.exe with SYSTEM privileges. The utility downloads addon contents into %TEMP%\sandboxie-updater, a directory that any unprivileged user can write to.

UpdUtil.exe validates files.cab by comparing its hash against the signed addon manifest. After verification succeeds, control passes to install.bat, which extracts files.cab and executes config.exe from inside the cabinet. The privileged process never re-validates the file before extraction.

This gap between hash check and file use creates the TOCTOU window. Because the staging directory is writable by the calling user, the attacker does not need to defeat any access controls or trigger a UAC prompt.

Root Cause

The root cause is reliance on a non-protected staging path for privileged execution. Sandboxie-Plus performs integrity validation on files.cab but does not lock the file, copy it to a SYSTEM-only location, or re-verify it before extraction and config.exe execution. The state of the file at time-of-check is assumed to persist until time-of-use.

Attack Vector

A local unprivileged user initiates an addon installation through SandMan. While UpdUtil.exe performs hash verification, the attacker monitors %TEMP%\sandboxie-updater and replaces files.cab with a malicious cabinet immediately after validation but before install.bat invokes extraction. The crafted cabinet contains a malicious config.exe, which install.bat executes in the SYSTEM security context. User interaction is required to start the addon install, but no privilege escalation prompt is shown.

See the GitHub Security Advisory GHSA-xjvp-63f2-v585 for the maintainer write-up.

Detection Methods for CVE-2026-34596

Indicators of Compromise

  • Unexpected file replacement events in %TEMP%\sandboxie-updater\files.cab between UpdUtil.exe hash verification and install.bat execution.
  • config.exe processes spawned from %TEMP%\sandboxie-updater running under the SYSTEM account.
  • Cabinet files in the updater directory whose contents do not match the published Sandboxie-Plus addon manifest.

Detection Strategies

  • Monitor process creation chains where SbieSvc.exe spawns UpdUtil.exe followed by cmd.exe or install.bat and a child config.exe running as SYSTEM.
  • Alert on file modifications to files.cab in user-writable temp directories that occur within milliseconds of a hash-validation read by a privileged process.
  • Hunt for SYSTEM-level processes whose image path resolves under %TEMP% or %LOCALAPPDATA%, which is rarely legitimate.

Monitoring Recommendations

  • Enable Windows Sysmon Event IDs 1 (process creation) and 11 (file create) with rules covering sandboxie-updater paths.
  • Audit privileged child processes of SbieSvc and forward telemetry to a central data lake for retroactive hunting.
  • Track Sandboxie-Plus version inventory across endpoints to identify hosts still running 1.17.2 or earlier.

How to Mitigate CVE-2026-34596

Immediate Actions Required

  • Upgrade Sandboxie-Plus to version 1.17.3 or later on every Windows host where it is installed.
  • Restrict addon installation to administrators until the patched build is deployed across the environment.
  • Audit endpoints for prior SYSTEM-level executions of config.exe originating from %TEMP%\sandboxie-updater.

Patch Information

The Sandboxie-Plus maintainers released version 1.17.3 to address this TOCTOU condition. Refer to the GitHub Security Advisory GHSA-xjvp-63f2-v585 for the official fix details and download links.

Workarounds

  • Block standard users from launching addon installations through SandMan via group policy or application control.
  • Apply Access Control Lists (ACLs) restricting write access to %TEMP%\sandboxie-updater while installation is in progress.
  • Remove SbieSvc autostart on systems where Sandboxie-Plus is not actively required until patching completes.
bash
# Verify installed Sandboxie-Plus version on Windows
(Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" | 
  Where-Object { $_.DisplayName -like "*Sandboxie*" }) |
  Select-Object DisplayName, DisplayVersion

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.