Quick answers
- Is CVE-2026-78380 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78380 being exploited in the wild.
- How severe is CVE-2026-78380?
- Informational severity, published 24 August 2026.
- Which products and versions are affected?
- RansomLook.
- Is there a fix for CVE-2026-78380?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78380 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-78380?
- Check whether anything you run is named in the advisory. 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
RansomLook fails to enforce privacy status when distributing newly collected victim posts to external notification channels and feeds. The vulnerability stems from incomplete privacy checks: the post-processing logic verifies individual posts are marked private, but neglects to validate the privacy status of the parent group or market. Additionally, the public MISP feed determination relied on groupinfo() which only checked the group database and did not evaluate market-level privacy flags. An attacker with access to public notification channels or the MISP feed can retrieve victim information configured as private. The fix introduces a centralized is_private_entity() check covering both groups and markets, preventing distribution of private entity posts through external channels while preserving internal storage and alerting.
Affected products
- RansomLook
Timeline
- 2026-08-24: disclosed