Path Traversal in Streambert (CVE-2026-52872)
Summary
Path traversal in Streambert (CVE-2026-52872). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.5.0 or later.
Original description
The description as published by the source.
Streambert is a cross-platform Electron Desktop App to stream and download video content. Prior to 2.5.0, the downloadSubtitleFile utility in src/ipc/downloads.js, reached through the run-download IPC channel, accepts a renderer-supplied subtitle url using the file: URI scheme and passes its decoded pathname to fs.copyFileSync. The renderer also controls downloadPath, which determines the destination path. A compromised renderer can therefore copy any file readable by the StreamBERT process into an attacker-chosen writable location, exposing sensitive local data, and can overwrite existing writable files. This vulnerability is fixed in 2.5.0.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-52872 has been found in Streambert.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Streambert to 2.5.0 or later.
If unsure, ask your IT team or search "Streambert CVE-2026-52872" on the vendor's site.
CVE-2026-52872 (Streambert) — CWE-22 / CVSS v3 8.8
Attack vector: local / no user interaction
Patched: 2.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in Streambert.
Check the vendor advisory for the affected versions of Streambert.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Streambert' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Streambert' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Streambertを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Streambert to 2.5.0ステージング環境で 2.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com