External risk intelligence

RansomLook Unauthenticated Database Export Information Disclosure.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-78370

The vulnerability exists in a web application endpoint (/export/<database>) accessible via the network. As this is a web-based service providing data exports, it is commonly deployed as an internet-facing application, making the endpoint reachable to remote users over the network.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a vulnerability in RansomLook's data export feature that could allow unauthorized remote access to sensitive information. The flaw in the legacy database export functionality means that certain private data, such as ransomware intelligence or victim details, might be exposed without proper authentication. The primary concern is to confirm if this system is in use and assess any potential exposure of private data.

  • Unauthenticated users may retrieve private data.
  • Protects sensitive ransomware intelligence and victim data.
  • Confirm RansomLook use and data privacy exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by accessing the RansomLook web application and sending a request to a specific export endpoint. This endpoint, due to an authorization flaw in its legacy database export functionality, allows unauthenticated remote users to retrieve sensitive information that should otherwise be restricted to authorized users. This can lead to the disclosure of private data contained within the application.

  • No authentication required.
  • Attacker requests specific export endpoint.
  • Exposure of private ransomware intelligence.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in RansomLook's legacy export functionality could allow unauthenticated remote users to access private information. When supported by the advisory, this may include details about groups, markets, posts, or other records that are intended to be kept private, potentially exposing sensitive ransomware intelligence or victim information.

  • Private group, market, and post data.
  • Unauthenticated access to export endpoint.
  • Disclosure of sensitive intelligence and victim data.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners are primarily responsible for addressing this authorization flaw in the RansomLook legacy database export functionality. The first practical step is to identify all instances of RansomLook, determine if the affected export endpoint is externally reachable or exposed, and confirm the accountable owner for each instance before planning remediation.

  • Application owners should address this flaw.
  • Verify external reachability of the export endpoint.
  • Plan remediation based on exposure and criticality.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is RansomLook?

RansomLook is a specialized web application used for managing and tracking sensitive intelligence related to ransomware operations. It serves as a centralized repository where organizations store critical data, including details about victim information, ransomware groups, and internal market tracking. Because it handles confidential records intended for restricted internal use, maintaining strict access control is essential to its primary function.

How does CVE-2026-78370 expose private data?

This vulnerability involves a weakness known as Missing Authorization (CWE-862). In RansomLook, the legacy database export functionality fails to verify the identity of the user requesting data. Because the application does not perform consistent access checks on these specific export endpoints, it treats requests from unauthorized users as if they were valid, allowing them to download private records that were supposed to remain hidden.

Do I need to be logged in to trigger this bug?

No. The vulnerability specifically affects the legacy export endpoint, which operates without requiring any authentication. An attacker does not need a user account, valid credentials, or administrative privileges to request the data. Simply reaching the web application over the network is sufficient to initiate the unauthorized export; legitimate authenticated actions are not required to trigger the information disclosure.

Is my RansomLook instance at high risk?

If your instance is internet-facing, it is at higher risk. Halo Surface Signal identifies that this vulnerability is reachable over the network via the /export/ endpoint. If your RansomLook installation is exposed to the internet, remote actors can potentially access the data. You should prioritize checking if your deployment is accessible from outside your private network and confirm if this legacy export feature is active.

How should I start securing my RansomLook installation?

Begin by auditing your environment to locate all active RansomLook instances and determine which ones are reachable from the internet. Once you have identified these instances, determine who is responsible for each deployment. The patch replaces the legacy export route with a centralized authorization system, so you must plan to update the software and ensure that all existing API keys are explicitly re-granted private-data access permissions.

References