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

New CVE Detected

CVE-2026-78372 – Missing Authorization / Sensitive Data Disclosure – RansomLook ≤ 2.0.0

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

Summary

CVE-2026-78372 is a missing authorization vulnerability (CWE-862) in RansomLook, an open-source ransomware activity tracking and aggregation platform. The flaw allows unauthenticated, remote attackers to access private group, market, and ransom-note data — including names, note content, metadata, post counts, and uptime statistics — that the application is designed to restrict. The issue carries a CVSS v4.0 score of 9.2 (Critical), reflecting network exploitability with no authentication or privileges required and a high confidentiality impact.

Technical details

  • Root cause: RansomLook does not consistently enforce authorization/privacy checks across its web views and API endpoints. Filtering logic that is supposed to exclude private groups, markets, and their associated ransom notes from public output is missing or incomplete in several code paths.
  • Trigger conditions: No authentication is required. An attacker simply needs to know or guess a private group/market slug, or use the exposed /compare feature and search/API endpoints, to retrieve restricted data.
  • Attack vector: Network — exploitable remotely over HTTP against the RansomLook web application and its API.
  • Impact:
    • The /compare endpoint permits direct querying of private entities, returning post counts and uptime data that should not be publicly visible.
    • Ransom-note detail views and search results can expose private group names, ransom-note content, and related metadata to unauthenticated users.
    • API endpoints for group listing, recent notes, group-specific notes, and individual note retrieval could return data belonging to private groups/markets without an authorization check.
    • Successful exploitation results in disclosure of confidential threat-intelligence data (e.g., ransomware group/market identities and note contents) that operators intended to keep private, which may undermine ongoing investigations or expose sensitive sourcing.

Affected software

  • Product: RansomLook (RansomLook/RansomLook on GitHub)
  • Affected versions: All versions from the initial release through 2.0.0 (inclusive)

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

Mitigation and recommended actions

  • Immediate: Upgrade RansomLook to a version that includes the authorization fix (commit dc92d6d5c076bcdbf3476aca42daf0260e8d99d7 and later), which introduces centralized private-group/note slug filtering (get_private_group_slugs(), get_private_note_slugs(), note_is_private()) and enforces it across the /compare endpoint, note detail views, search, and the notes API. Confirm the running instance is on a patched release before considering it remediated.
  • If immediate patching is not possible:
    • Restrict network access to self-hosted RansomLook instances (e.g., place behind authentication, VPN, or IP allow-listing) so that only trusted users can reach the web application and API.
    • Audit any configured "private" groups/markets and review logs for unusual /compare, search, or API requests referencing those group/market slugs.
    • Temporarily disable or restrict the /compare feature and public API endpoints if private groups are configured and patching cannot be applied promptly.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge