CVE-2026-52877: truelockmc streambert · Improper Input Validation
Affects truelockmc streambertSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 2.6.0 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.6.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade streambert and truelockmc/streambert to 2.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| truelockmcstreambert | Affected
| Fixed in
|
GitHubtruelockmc/streambertpkg:github/truelockmc/streambertOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Streambert to version 2.6.0 or later, where the open-external IPC handler validates URL protocols before passing them to Electron's shell.openExternal. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-52877 is an improper input validation vulnerability in the Streambert Electron desktop app before version 2.6.0. The flaw allows a compromised renderer process to pass unvalidated URLs to Electron's shell.openExternal function, potentially causing the host to open local files or launch external applications via custom URI schemes. This vulnerability is fixed in version 2.6.0.