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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Remove/disable the legacy unauthenticated export route so that /export/<database> requires authorization and cannot be accessed by unauthenticated remote users.
RansomLook legacy database export (/export/<database>) Unauthenticated access to export endpoints = disabled - Configuration
Update authorization so API keys must be explicitly granted private-data access; existing keys do not automatically receive this privilege.
RansomLook centralized authorization Private-data access privilege for API keys = explicitly granted - Configuration
Apply the same private-data filtering consistently across both API responses and database exports, ensuring exportable databases do not return private entities to unauthorized requesters.
RansomLook private-entity filtering (API + database exports) Private-data filtering consistency = enforced
Event History
Frequently Asked Questions
Who can access the exposed information?
Any unauthenticated remote user who can reach the RansomLook web application can request the affected export endpoint. No account or prior authorization is required.
What data may be included in an export?
Exports may include records marked private, including information associated with groups, markets, posts, and other records. Depending on the instance contents, this can include private ransomware intelligence, victim information, and internal tracking data.
Why do existing export filters not prevent this exposure?
Some entity databases receive limited filtering, but other exportable databases are returned directly. The legacy route does not consistently enforce the application's private-entity access restrictions.
What does the fix change?
The patch removes the legacy unauthenticated export route and adds centralized authorization handling that distinguishes ordinary authenticated API access.