dbcve.org
RansomlookApplication

CVE-2026-40584

HIGH · 7.5 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 1.9.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
RansomLook is a tool to monitor Ransomware groups and markets and extract their victims. Prior to 1.9.0, the API in the affected application improperly filters private location entries in website/web/api/genericapi.py. Because the code removes elements from a list while iterating over it, entries marked as private may be unintentionally retained in API responses, allowing unauthorized disclosure of non-public location information. This vulnerability is fixed in 1.9.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The API endpoint in genericapi.py has a logic flaw where private location entries are supposed to be filtered before being returned in API responses. The code incorrectly modifies a list while iterating over it (a classic Python anti-pattern), causing the filtering to fail silently and leak non-public location data to unauthorized callers.

MitigationUpgrade to RansomLook version 1.9.0, which corrects the list iteration logic to properly filter private location entries before API responses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RansomlookApplication
Affected:< 1.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ransomlook installation and version
    Locate the Ransomlook installation and determine its version number (e.g., check package metadata, setup.py, __init__.py, or version file)
    Affected if Installed version is below 1.9.0
  2. Locate the genericapi.py file
    Find the genericapi.py file within the Ransomlook installation directory structure
    Affected if The file exists and is part of the installed version
  3. Inspect the list iteration code pattern
    Open genericapi.py and search for code that modifies a list while iterating over it, particularly related to location filtering logic
    Affected if The file contains a loop that modifies a list during iteration when handling private location entries
  4. Verify the API endpoint is accessible
    Confirm that the API endpoint handled by genericapi.py is exposed and reachable (check if the API service is running and network-accessible)
    Affected if The API endpoint is active and accepts requests
  5. Check for private location data in the system
    Examine the data store to determine if private location entries exist in the system that should be filtered from API responses
    Affected if Private/non-public location data exists in the database that would be incorrectly returned due to the filtering failure

A user is affected if they are running Ransomlook version below 1.9.0 with the vulnerable genericapi.py code, where the API is accessible and private location data exists in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.0 or later
Fixed in 1.9.0
Interim mitigation

Upgrade to RansomLook version 1.9.0, which corrects the list iteration logic to properly filter private location entries before API responses.

Recommended fix High confidence

1.9.0

  1. 1. Identify the current installed version of Ransomlook (e.g., run `pip show ransomlook` or check your package manager)
  2. 2. Upgrade Ransomlook to version 1.9.0 or later using pip: `pip install --upgrade ransomlook`
  3. 3. If installed from source, navigate to the repository and pull the latest code or checkout version 1.9.0: `git pull` or `git checkout 1.9.0`
  4. 4. Verify the upgrade was successful by checking the version: `pip show ransomlook`
  5. 5. Test the API functionality to confirm the private location filtering now works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ransomlook Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40584 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data