---
id: CVE-2026-78370
title: >-
  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 inter…
summary: >-
  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 inter…
severity: none
cwe:
  - CWE-862
published: '2026-08-24'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T13:10:00.187'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-78370'
references:
  - url: >-
      https://github.com/RansomLook/RansomLook/commit/ff97a3489d70ffc3c1d09ea2c7d25137edfffb2a
    label: 5a6e4751-2f3f-4070-9419-94fb35b644e8
tags:
  - nvd
epss: 0.00687
epssPercentile: 0.51406
ingestedAt: '2026-10-14T13:30:58.559Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.