Quick answers
- Is CVE-2026-48046 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48046 being exploited in the wild.
- How severe is CVE-2026-48046?
- Informational severity, with a CVSS score of 9.3, published 11 August 2026.
- Which products and versions are affected?
- Truelockmc Streambert <2.5.0.
- Is there a fix for CVE-2026-48046?
- A patch was published on 2026-05-22: Version 2.5.0 released with patch implementing URL whitelist validation Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48046 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48046?
- 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 exists in the IPC handler "download-and-install-update" (src/ipc/player.js) which accepts a user-controlled URL parameter from the renderer process without validation. An attacker who can compromise the renderer process (via XSS or untrusted content) can invoke this handler with a malicious URL pointing to an attacker-controlled binary. The application then downloads and automatically executes this binary using spawn(). The vulnerability requires compromising the renderer process first, but provides a direct path from renderer context to arbitrary code execution with application privileges. Version 2.5.0 patches the issue by restricting downloads to the official GitHub release URL using a trusted prefix whitelist.
Affected products
- truelockmc Streambert <2.5.0
Timeline
- 2026-05-22: disclosed: GHSA-vj74-r9xm-37mj advisory published; vulnerability discovered by jeremyHOT
- 2026-05-22: patched: Version 2.5.0 released with patch implementing URL whitelist validation