Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-64721 is a critical-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Sandboxie-Plus Sandboxie. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 50% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-64721 is a heap overflow vulnerability (CWE-190) in Sandboxie, a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. It affects versions 1.16.6 and prior, specifically within the SYSTEM-level service SbieSvc.exe. The issue arises in the SbieIniServer::RC4Crypt handler, which exposes functionality to sandboxed processes and adds a fixed header size to a caller-controlled value_len parameter without overflow checking. A large value_len, such as 0xFFFFFFF0, causes the allocation size to wrap around, resulting in an undersized buffer into which attacker-controlled data is copied, triggering the overflow. The vulnerability carries a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
Sandboxed processes can exploit this vulnerability remotely over the network with low complexity and no privileges required. An attacker running malicious code within a Sandboxie-isolated environment can supply a crafted value_len to trigger the heap overflow in SbieSvc.exe, enabling arbitrary code execution with SYSTEM privileges on the host system. This fully compromises the host, bypassing the sandbox isolation entirely.
Sandboxie addresses this issue in version 1.16.7, as detailed in the project's GitHub security advisory (GHSA-w476-j57g-96vp), release notes, and the fixing commit (000492f8c411d24292f1b977a107994347bc7dfa). Security practitioners should update to 1.16.7 or later to mitigate the risk.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-202846
Vulnerability Data
Sandboxie 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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.