dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-48055

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Streambert is a cross-platform Electron Desktop App to stream and download any video media. In versions 2.4.0 and prior, a high-severity Zip Slip vulnerability was identified in Streambert's subtitle extraction logic. The application does not sanitize archive entry filenames during extraction, allowing a malicious archive to perform path traversal and write arbitrary files to the host filesystem. The subtitle extraction process downloads a ZIP archive and extracts its entries. The destination file path is constructed by concatenating the raw archive entry name (extracted.name) directly to the temporary directory path. If a malicious ZIP archive containing directory traversal sequences is processed, it escapes the temporary directory boundaries. The application then writes the extracted payload anywhere on the host filesystem subject to the application's current write permissions. This issue has been fixed in version 2.5.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Streambert versions 2.4.0 and prior contain a Zip Slip vulnerability in the subtitle extraction feature. The application constructs destination file paths by directly concatenating raw archive entry names (extracted.name) to a temporary directory path without sanitization, allowing malicious ZIP archives with directory traversal sequences (e.g., '../../../etc/passwd') to escape the intended directory and write arbitrary files to the host filesystem.

MitigationUpgrade to Streambert version 2.5.0 or later, which implements proper path sanitization for archive entry filenames during extraction.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Streambert installation and version
    Run 'streambert --version' or check the application's about/help screen to confirm the installed version is 2.4.0 or lower
    Affected if Installed version is 2.4.0 or prior
  2. Locate Streambert configuration directory
    Search for the application data directory where Streambert stores settings and temporary extraction folders, commonly in user home directories under '.streambert' or similar
    Affected if Configuration directory exists and contains extraction temp folders
  3. Verify subtitle extraction feature usage
    Check if the application has been used to extract subtitles from ZIP archives - look for recent extraction history files, logs, or the presence of extracted subtitle files
    Affected if Subtitle extraction from ZIP archives has been performed using the application
  4. Inspect application logs for extraction behavior
    Examine Streambert's log files for entries containing 'subtitle', 'extract', 'zip', or archive-related operations to confirm the vulnerable feature is active
    Affected if Logs show ZIP archive extraction activity without evidence of path validation

A user is affected if Streambert version 2.4.0 or prior is installed and the subtitle extraction feature has been used with ZIP archives, as the vulnerable code path concatenates unsanitized archive entry names to destination directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Streambert version 2.5.0 or later, which implements proper path sanitization for archive entry filenames during extraction.

Recommended fix High confidence

2.5.0

  1. Upgrade Streambert to version 2.5.0 or later to obtain the fixed code with sanitized archive entry filename validation
  2. Verify the upgrade was successful by checking the application version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48055 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48055 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data