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

New CVE Detected

CVE-2026-78386 – Sensitive Information Disclosure – RansomLook ≤ 2.0.0

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

Summary

CVE-2026-78386 is a sensitive information disclosure vulnerability (CWE-200) in RansomLook, an open-source ransomware leak-site tracking tool. The RansomLook API exposed internal, operator-side "location" record fields — including scraping authentication headers/cookies, CAPTCHA/paywall bypass scripts, and the scraping browser engine used — to unauthenticated remote users. The issue carries a CVSS score of 8.7 (High).

Technical details

  • Root cause: The RansomLook API implementation (website/web/api/genericapi.py) returned complete internal "location" database records to API callers without filtering out operator-only fields, rather than restricting responses to a defined set of public fields.
  • Sensitive fields exposed: header (cookies and authorization headers used to scrape a given leak site), init_script (logic used to defeat a target’s CAPTCHA or paywall), and browser (the scraping engine/browser used).
  • Trigger conditions: Any unauthenticated client issuing standard requests to the affected API endpoints that return location objects would receive these internal fields in the response — no special privileges or user interaction required.
  • Attack vector: Network — the flaw is remotely exploitable over the API with no authentication.
  • Impact: Disclosure of this data would let an attacker replay the leaked scraping credentials/session cookies to impersonate the RansomLook scraper, or use the disclosed bypass logic to patch/defeat the target site’s anti-scraping (CAPTCHA/paywall) protections, undermining the integrity of RansomLook’s monitoring capability and potentially exposing the scraping infrastructure to disruption or detection countermeasures.

Affected software

  • RansomLook (https://github.com/RansomLook/RansomLook) — all versions from initial release through 2.0.0 (semver range "0 through 2.0.0")

Severity

  • CVSS v4.0: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • Key drivers: network attack vector, low attack complexity, no privileges or user interaction required, high confidentiality impact.

Mitigation and recommended actions

  • Immediate: Upgrade RansomLook to a version that includes the fix delivered in commit cc9182930306ff36c7b3424817d49f18df3c85d1, which introduces a _PUBLIC_LOCATION_FIELDS allowlist and a _public_location() filtering function so that only non-sensitive fields (slug, fqdn, title, version, available, updated, lastscrape, fs, chat, admin, screen, source) are returned by public-facing API endpoints.
  • If immediate patching is not possible:
    • Restrict network access to the RansomLook API to trusted internal hosts only (e.g., via firewall rules or a reverse proxy requiring authentication).
    • Rotate any scraping credentials, session cookies, and authorization headers currently configured in RansomLook location records, as they should be considered compromised if the API has been publicly reachable.
    • Review CAPTCHA/paywall bypass (init_script) logic for exposure and consider disabling or updating it for actively monitored sites until patched.
    • Monitor API access logs for anomalous or bulk requests to location-related endpoints that could indicate reconnaissance or prior exploitation.

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