# CVE-2026-52873: Streambert: Global CSP Removal in Wyzie Redeem Window Enables Unconstrained XSS in Electron Renderer

> Attackers can execute arbitrary JavaScript in the Electron renderer by exploiting missing CSP and window restrictions in the Wyzie redeem window.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-2j2q-qvpf-wh43

## What is CVE-2026-52873?

CVE-2026-52873 is a medium-severity cross-site scripting vulnerability in truelockmc streambert, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Streambert is a cross-platform Electron Desktop App to stream and download video content. From version 2.5.0 until version 2.6.0, the wyzie-open-redeem IPC handler in index.js creates the partition:wyzie-redeem Electron session and registers an onHeadersReceived hook that removes the Content-Security-Policy header from every response in that session. The redeem window also lacks a setWindowOpenHandler restriction, so script injection in sub.wyzie.io, a loaded third-party resource, or a site reached through navigation executes without CSP constraints and can affect additional windows and persistent session storage. A user must open the Wyzie API key redemption window, and exploitation requires attacker-controlled script content in a loaded page. The resulting renderer script can invoke renderer-exposed application functionality and can be chained with other vulnerabilities to access internal services or sensitive data. This issue is fixed in version 2.6.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2026-52873?


## How do I fix CVE-2026-52873?

No fix has been published for CVE-2026-52873 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-52873 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52873 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52873 and fix it if it is affected.

What it is: CVE-2026-52873 is a medium-severity cross-site scripting vulnerability in truelockmc streambert, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52873 exists.

Affected product: truelockmc streambert. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52873/ (Markdown: https://insights.sbomify.com/CVE-2026-52873/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52873
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52873
- OSV: https://osv.dev/vulnerability/CVE-2026-52873

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52873/
Summaries are generated and may contain mistakes; the official description above is the record.