Quick answers
- Is CVE-2026-34459 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34459 being exploited in the wild.
- How severe is CVE-2026-34459?
- High severity, with a CVSS score of 8.8, published 5 May 2026.
- Which products and versions are affected?
- Sandboxie-Plus <= 1.17.2.
- Is there a fix for CVE-2026-34459?
- A patch was published on 2026-05-05: Fixed in version 1.17.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34459 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-34459?
- Check whether you run Sandboxie-Plus Sandboxie or Sandboxie-Plus at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists within the SbieSvc proxy service's GetRawInputDeviceInfoSlave handler in core/svc/GuiServer.cpp. It consists of two flaws that can be chained: an uninitialized stack memory leak and a stack-based buffer overflow. First, by sending an IPC request with cbSize set to 0, the handler returns up to 32KB of uninitialized stack memory, allowing an attacker to leak return addresses and stack cookies to bypass ASLR and /GS protections. Second, the handler performs a memcpy using an attacker-controlled length without bounds checking against the 32KB stack buffer. An attacker can use the leaked information to craft a ROP chain that achieves SYSTEM-level code execution. While Intel CET (Hardware-enforced shadow stacks) can mitigate the ROP execution, it does not prevent the information leak. The issue is fixed in version 1.17.3.
Affected products
- sandboxie-plus Sandboxie-Plus <= 1.17.2
Timeline
- 2026-05-04: advisory: Vendor advisory published on GitHub
- 2026-05-05: disclosed: CVE published to NVD
- 2026-05-05: patched: Fixed in version 1.17.3