Quick answers
- Is CVE-2026-78370 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78370 being exploited in the wild.
- How severe is CVE-2026-78370?
- Informational severity, with a CVSS score of 5.3, published 24 August 2026.
- Which products and versions are affected?
- RansomLook before 2.0 (patch date 2026-08-23).
- Is there a fix for CVE-2026-78370?
- A patch was published on 2026-08-23: Patch committed removing unauthenticated export route Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78370 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-78370?
- Check whether you run RansomLook at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in the legacy /export/<database> endpoint that fails to enforce authentication and consistent access control. The endpoint permits direct export of internal databases without requiring API credentials, and while some entity types receive limited filtering, private records (groups, markets, posts) are returned unfiltered, bypassing the application's private-entity restrictions. An unauthenticated network-reachable attacker can invoke the endpoint to retrieve sensitive data that should only be accessible to authorized API consumers. The patch removes the unauthenticated export route, implements centralized authorization logic, and requires explicit per-API-key authorization for private-data access.
Affected products
- RansomLook RansomLook before 2.0 (patch date 2026-08-23)
Timeline
- 2026-08-24: disclosed: CVE-2026-78370 published
- 2026-08-23: patched: Patch committed removing unauthenticated export route