CVE-2026-52875

{"id": "CVE-2026-52875", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-52875", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-25T01:44:23.740314Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.4, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "HIGH", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "LOW", "vulnConfidentialityImpact": "LOW", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "truelockmc", "product": "streambert", "versions": [{"status": "affected", "version": "< 2.6.0"}]}]}], "published": "2026-08-18T22:16:54.003", "references": [{"url": "http://github.com/truelockmc/streambert/commit/43566ed031183b046675761c9813c5379b619269", "source": "security-advisories@github.com"}, {"url": "https://github.com/truelockmc/streambert/pull/149", "source": "security-advisories@github.com"}, {"url": "https://github.com/truelockmc/streambert/security/advisories/GHSA-c64m-cx97-6rc9", "source": "security-advisories@github.com"}, {"url": "https://github.com/truelockmc/streambert/security/advisories/GHSA-c64m-cx97-6rc9", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-22"}, {"lang": "en", "value": "CWE-73"}]}], "descriptions": [{"lang": "en", "value": "Streambert is a cross-platform Electron Desktop App to stream and download video content. Prior to 2.6.0, the perform-scheduled-backup IPC handler in src/ipc/storage.js takes settings.path from a renderer-supplied object and uses the resulting directory for fs.mkdirSync, fs.writeFileSync, fs.readdirSync, and fs.unlinkSync operations without checking that it is inside an authorized backup location. A compromised renderer can choose an absolute path or a relative traversal path to create directories and write a streambert-backup-[timestamp].json file containing renderer-controlled data. The pruning loop can also delete files in that directory whose names begin with streambert-backup- and end with .json. This vulnerability is fixed in 2.6.0."}, {"lang": "es", "value": "Streambert es una aplicaci\u00f3n de escritorio Electron multiplataforma para transmitir y descargar contenido de video. Antes de la versi\u00f3n 2.6.0, el gestor IPC perform-scheduled-backup en src/ipc/storage.js toma settings.path de un objeto proporcionado por el renderizador y utiliza el directorio resultante para operaciones de fs.mkdirSync, fs.writeFileSync, fs.readdirSync y fs.unlinkSync sin verificar que est\u00e9 dentro de una ubicaci\u00f3n de copia de seguridad autorizada. Un renderizador comprometido puede elegir una ruta absoluta o una ruta de recorrido relativa para crear directorios y escribir un archivo streambert-backup-[timestamp].json que contiene datos controlados por el renderizador. El bucle de poda tambi\u00e9n puede eliminar archivos en ese directorio cuyos nombres comienzan con streambert-backup- y terminan con .json. Esta vulnerabilidad se corrige en la versi\u00f3n 2.6.0."}], "lastModified": "2026-10-22T17:09:59.477", "sourceIdentifier": "security-advisories@github.com"}