CVE-2025-64721
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. In versions 1.16.6 and below, the SYSTEM-level service SbieSvc.exe exposes SbieIniServer::RC4Crypt to sandboxed processes. The handler adds a fixed header size to a caller-controlled value_len without overflow checking. A large value_len (e.g., 0xFFFFFFF0) wraps the allocation size, causing a heap overflow when attacker data is copied into the undersized buffer. This allows sandboxed processes to execute arbitrary code as SYSTEM, fully compromising the host. This issue is fixed in version 1.16.7.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSandboxie's SYSTEM-level service SbieSvc.exe exposes SbieIniServer::RC4Crypt to sandboxed processes without proper integer overflow checking. The handler adds a fixed header size to a caller-controlled value_len, and when value_len is large (e.g., 0xFFFFFFF0), the allocation size wraps around, creating an undersized buffer. Copying attacker-controlled data into this undersized buffer causes a heap overflow, allowing sandboxed processes to execute arbitrary code as SYSTEM and fully compromise the host.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.14.0, < 1.16.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Sandboxie Plus is installedCheck for Sandboxie Plus in installed programs via Control Panel > Programs and Features, or locate the SbieSvc.exe executable in the Sandboxie installation directory (typically C:\Program Files\Sandboxie-Plus or C:\Program Files\Sandboxie)Affected if Sandboxie Plus is present on the system
-
Determine installed Sandboxie Plus versionRight-click SbieSvc.exe in the Sandboxie installation directory, select Properties, and view the File Version information on the Details tab. Alternatively, run 'sandman_zh-CN.exe --version' or check Help > About in Sandboxie Plus GUI if available.Affected if Version is 1.14.0 or higher but lower than 1.16.7
-
Confirm SbieSvc.exe service exists and is runningOpen Services console (services.msc) and verify that a Sandboxie service (typically named 'Sandboxie Service' or 'SbieSvc') exists and its Status shows 'Running'. Or run 'sc query SbieSvc' from command prompt.Affected if The Sandboxie service exists and is running, enabling the vulnerable code path
-
Verify the RC4Crypt interface is accessible to sandboxed processesBy default, the SbieIniServer RPC interface is exposed to sandboxed processes. No configuration change is needed for exploitation if the service is running. Confirm the vulnerable SbieIniServer component is loaded by observing SbieSvc.exe active connections via Process Monitor or by checking that sandboxed applications can access Sandboxie API functions.Affected if The Sandboxie service is running and accessible to sandboxed applications, which is the default configuration
A system is affected if Sandboxie Plus version 1.14.0 through 1.16.6 is installed and the SbieSvc.exe service is running, as the integer overflow in SbieIniServer::RC4Crypt becomes exploitable under these conditions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.16.7
Upgrade Sandboxie to version 1.16.7 or later to patch the integer overflow vulnerability in SbieIniServer::RC4Crypt.
Sandboxie 1.16.7
- Download Sandboxie version 1.16.7 or later from the official source
- Close all Sandboxie-related processes and services
- Install the new version, ensuring the SbieSvc.exe service is updated
- Restart the Sandboxie service or reboot the system
- Verify the installed version is 1.16.7 or higher by checking the program's version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64721 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64721 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data