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), andbrowser(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_FIELDSallowlist 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.

