Quick answers
- Is CVE-2026-78378 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78378 being exploited in the wild.
- How severe is CVE-2026-78378?
- Informational severity, published 24 August 2026.
- Which products and versions are affected?
- RansomLook RansomLook.
- Is there a fix for CVE-2026-78378?
- 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-78378 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-78378?
- Check whether you run RansomLook. 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 a Redis glob pattern injection caused by insufficient input sanitization in multiple endpoints. When user-supplied input (such as group names or blockchain identifiers) fails to match known values, the application directly interpolates the attacker-controlled value into Redis SCAN MATCH patterns without escaping glob metacharacters (*, ?, [, ]). This allows attackers to broaden SCAN operations beyond their intended scope. The /api/health/<name> endpoint is vulnerable to enumeration attacks; /api/crypto/chain/<chain> exhibits the same flaw; and the delete_manual_torrent() function's use of attacker-influenced infohash values creates a destructive sink where arbitrary torrent-health data could be deleted. No authentication is required to exploit the enumeration variants. The patch escapes user-controlled glob characters before Redis interpolation and removes unsafe fallback behavior.
Affected products
- RansomLook RansomLook
Timeline
- 2026-08-24: disclosed