Quick answers
- Is CVE-2026-48056 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48056 being exploited in the wild.
- How severe is CVE-2026-48056?
- Critical severity, with a CVSS score of 10, published 11 August 2026.
- Which products and versions are affected?
- Truelockmc Streambert < 2.5.0.
- Is there a fix for CVE-2026-48056?
- A patch was published on 2026-05-22: Version 2.5.0 released with patch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48056 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48056?
- Check whether you run Truelockmc Streambert 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 is an improper input validation flaw (CWE-20) in the run-download IPC handler located in src/ipc/downloads.js. The handler accepts a binaryPath argument from the renderer process and executes it via Node.js spawn without validating the file path, enabling a compromised renderer (via XSS or malicious feed injection) to execute arbitrary local binaries such as cmd.exe, powershell.exe, or /bin/sh with the application's privileges. The attack requires the renderer process to be compromised but does not require additional user interaction. Version 2.5.0 patches the vulnerability by validating that the binary path resides in a legitimate downloader directory containing an _internal subdirectory.
Affected products
- truelockmc Streambert < 2.5.0
Timeline
- 2026-05-22: disclosed
- 2026-05-22: patched: Version 2.5.0 released with patch