Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-78370 – Unauthenticated Sensitive Data Exposure – RansomLook ≤ 2.0.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-78370 is a missing-authorization vulnerability in RansomLook, the open-source ransomware intelligence tracking platform. The flaw resides in a legacy database export endpoint that allows unauthenticated users to retrieve internal databases — including data explicitly marked private — without any access control checks. The issue carries a CRITICAL CVSS score of 9.2 and affects RansomLook versions 0 through 2.0.0.

Technical details

  • Root cause: The /export/<database> endpoint in RansomLook’s legacy export functionality does not consistently enforce the application’s private-entity access restrictions, allowing any caller to pull internal database contents.
  • Trigger conditions: An attacker simply needs to send a request to the /export/<database> route on a reachable RansomLook instance; no credentials, API key, or user interaction are required.
  • Attack vector: Network-based, low complexity, no privileges or user interaction required (CVSS AV:N/AC:L/AT:N/PR:N/UI:N).
  • Impact: Unauthorized disclosure of sensitive ransomware intelligence, victim information, and other internal tracking records that were designated as private, resulting in high confidentiality impact to the underlying data store (VC:H, SC:H). No integrity or availability impact was reported.
  • Root fix: The vendor removed the unauthenticated export route entirely and replaced it with centralized authorization logic that requires explicit private-data access grants tied to API keys, rather than relying on the legacy export path.

Affected software

  • RansomLook versions 0 through 2.0.0 (inclusive), per semantic versioning.

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical)
  • Vector: 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
  • CWE-862: Missing Authorization

Mitigation and recommended actions

  • Immediate: Upgrade RansomLook to a version containing the fix that removes the unauthenticated /export/<database> route and enforces centralized, API-key-based authorization for private-data access. Confirm the deployed instance no longer exposes the legacy export endpoint after upgrading.
  • If immediate patching is not possible:
    • Restrict network access to the RansomLook web interface and API to trusted/internal networks only (e.g., via firewall rules, VPN, or reverse-proxy allowlisting).
    • Disable or block the /export/<database> route at the reverse proxy or web server layer until the patched version is deployed.
    • Audit access logs for requests to /export/ paths to identify potential prior exploitation or data exfiltration attempts.
    • Review any data previously exposed via this endpoint and rotate/notify as appropriate if private records may have been accessed by unauthorized parties.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge