Arbitrary binary execution via unvalidated IPC path
Published Aug 11, 2026 · Updated Aug 11, 2026
Arbitrary binary execution in Streambert before 2.5.0 allows remote attackers to execute local programs through the downloader IPC handler. The run-download handler in src/ipc/downloads.js passes the renderer-controlled binaryPath directly to Node.js spawn without validating its directory. A renderer compromise, such as XSS or remote feed injection, is required; the selected binary then runs with the desktop application's privileges.
Summary
What happened
Arbitrary binary execution in Streambert before 2.5.0 allows remote attackers to execute local programs through the downloader IPC handler. The run-download handler in src/ipc/downloads.js passes the renderer-controlled binaryPath directly to Node.js spawn without validating its directory. A renderer compromise, such as XSS or remote feed injection, is required; the selected binary then runs with the desktop application's privileges.
The record
- CVE
- CVE-2026-48056
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- truelockmc
- Product
- Streambert
- Classifications
- CWE-749, CWE-20, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record 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=< 2.5.0
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
- Downloader IPC handler 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