CVE-2026-78370

{"id": "CVE-2026-78370", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-78370", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-24T17:27:00.875914Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.2, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/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": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "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": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "affectedData": [{"repo": "https://github.com/RansomLook/RansomLook/", "vendor": "ransomlook", "product": "ransomlook", "versions": [{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "2.0.0"}], "defaultStatus": "unaffected"}]}], "published": "2026-08-24T14:17:05.100", "references": [{"url": "https://github.com/RansomLook/RansomLook/commit/ff97a3489d70ffc3c1d09ea2c7d25137edfffb2a", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "description": [{"lang": "en", "value": "CWE-862"}]}], "descriptions": [{"lang": "en", "value": "RansomLook contains an authorization flaw in its legacy database export functionality that can allow unauthenticated remote users to retrieve information intended to remain private.\n\nThe /export/<database> endpoint permits selected internal databases to be exported without requiring authentication. While limited filtering is performed for some entity databases, other exportable databases are returned directly without consistently applying the application's private-entity access restrictions. As a result, information associated with groups, markets, posts, or other records marked as private may be included in an export accessible to an unauthenticated requester.\n\nAn attacker able to reach the RansomLook web application can request the affected export endpoint and retrieve data that should only be available to authorized users. Depending on the contents of the instance, this may disclose private ransomware intelligence, victim information, internal tracking data, or other information deliberately excluded from public views.\n\nThe patch removes the legacy unauthenticated export route and introduces centralized authorization handling that distinguishes ordinary authenticated API access from authorization to view private entries. API keys must now be explicitly granted private-data access, while existing keys do not automatically receive this privilege. The same private-data filtering is also applied consistently across API responses and database exports."}, {"lang": "es", "value": "RansomLook contiene una falla de autorizaci\u00f3n en su funcionalidad de exportaci\u00f3n de base de datos heredada que puede permitir a usuarios remotos no autenticados recuperar informaci\u00f3n destinada a permanecer privada.\n\nEl endpoint /export/<database> permite que bases de datos internas seleccionadas sean exportadas sin requerir autenticaci\u00f3n. Si bien se realiza un filtrado limitado para algunas bases de datos de entidades, otras bases de datos exportables se devuelven directamente sin aplicar consistentemente las restricciones de acceso a entidades privadas de la aplicaci\u00f3n. Como resultado, informaci\u00f3n asociada con grupos, mercados, publicaciones u otros registros marcados como privados puede incluirse en una exportaci\u00f3n accesible para un solicitante no autenticado.\n\nUn atacante capaz de alcanzar la aplicaci\u00f3n web RansomLook puede solicitar el endpoint de exportaci\u00f3n afectado y recuperar datos que solo deber\u00edan estar disponibles para usuarios autorizados. Dependiendo del contenido de la instancia, esto puede divulgar inteligencia privada de ransomware, informaci\u00f3n de v\u00edctimas, datos de seguimiento internos u otra informaci\u00f3n deliberadamente excluida de las vistas p\u00fablicas.\n\nEl parche elimina la ruta de exportaci\u00f3n no autenticada heredada e introduce un manejo de autorizaci\u00f3n centralizado que distingue el acceso ordinario autenticado a la API de la autorizaci\u00f3n para ver entradas privadas. Las claves de API ahora deben recibir expl\u00edcitamente acceso a datos privados, mientras que las claves existentes no reciben autom\u00e1ticamente este privilegio. El mismo filtrado de datos privados tambi\u00e9n se aplica consistentemente en las respuestas de la API y las exportaciones de bases de datos."}], "lastModified": "2026-10-14T13:10:00.187", "sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8"}