CVE-2026-78370: RansomLook Unauthenticated Database Export Exposes Private Data
RansomLook contains an authorization flaw in its legacy database export functionality that can allow unauthenticated remote users to retrieve information intended to remain private.
The /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.
An 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.
The 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.
Security readout for executives and security teams
Plain-English summary
RansomLook can expose records deliberately marked private through a legacy database-export endpoint that does not require login. Anyone able to reach an affected application could obtain sensitive ransomware intelligence, victim details, market or group records, posts, and internal tracking data. The issue affects confidentiality rather than data modification or service availability.
Executive priority
Treat reachable deployments as an immediate confidentiality incident-prevention priority. Patch or restrict the route promptly, determine what private information was stored, and review historical export activity. Escalate suspected disclosure through the organization’s incident-response process.
Technical view
CVE-2026-78370 is a CWE-862 missing-authorization flaw in /export/<database>. Some exportable databases bypass consistent private-entity filtering, allowing unauthenticated remote disclosure. The supplied CVSS 4.0 score is 9.2. The patch removes the legacy unauthenticated route, centralizes authorization, consistently filters private data, and requires explicit private-data permission for API keys.
Likely exposure
Highest risk applies to reachable RansomLook deployments retaining the legacy export route and storing private records. Internet-facing instances are especially exposed, but internally reachable instances may also be affected. The supplied affected-version data lists version "0" with default status "unaffected," so precise release boundaries require confirmation from project guidance or the deployed code.
Exploitation context
Exploitation requires network access but no authentication, privileges, user interaction, or unusual conditions. The source bundle does not report active exploitation, and the CVE is not listed as KEV. Absence from KEV does not prove exploitation has not occurred; review access history for unexpected exports.
Researcher notes
The core boundary failure is inconsistent authorization between public views, API responses, and exports. Remediation separates ordinary API authentication from permission to view private entities and denies that privilege to existing keys by default. Exact vulnerable release ranges and evidence of exploitation are not established in the supplied sources.
Mitigation direction
Apply the vendor patch represented by commit ff97a3489d70ffc3c1d09ea2c7d25137edfffb2a.
Until patched, prevent unauthenticated access to the legacy database-export route.
Review API keys and explicitly grant private-data access only where operationally required.
Consult RansomLook guidance for release-specific upgrade instructions and affected-version clarification.
Validation and detection
Inventory reachable RansomLook instances and identify deployments containing the legacy export route.
Confirm deployed code includes the cited authorization and private-filtering changes.
Verify existing API keys did not automatically receive private-data access.
Review application and proxy logs for unauthenticated or unexpected database-export requests.
Use authorized testing to confirm private records remain unavailable without explicit private-data permission.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.