SYSTEM code execution via RC4Crypt integer wrap
Published Dec 11, 2025 · Updated Dec 11, 2025
Integer overflow in SbieIniServer::RC4Crypt in Sandboxie-Plus Sandboxie before 1.16.7 allows local users to execute code as SYSTEM. The handler adds a fixed reply-header size to caller-controlled value_len without an overflow check, then copies attacker data into the wrapped, undersized heap allocation. Code must already run inside a Sandboxie sandbox and reach the service IPC; exploitation escapes containment, while the published proof of concept demonstrates a service crash.
Summary
What happened
Integer overflow in SbieIniServer::RC4Crypt in Sandboxie-Plus Sandboxie before 1.16.7 allows local users to execute code as SYSTEM. The handler adds a fixed reply-header size to caller-controlled value_len without an overflow check, then copies attacker data into the wrapped, undersized heap allocation. Code must already run inside a Sandboxie sandbox and reach the service IPC; exploitation escapes containment, while the published proof of concept demonstrates a service crash.
The record
- CVE
- CVE-2025-64721
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- Sandboxie-Plus
- Product
- Sandboxie
- Classifications
- CWE-190, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.16.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- RC4Crypt service-crash proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo