Redis Glob Pattern Injection Allows Unauthorized Enumeration of Private Ransomlook Data

Summary

Ransomlook contains a Redis glob pattern injection vulnerability caused by insufficient neutralization of user-controlled input before it is incorporated into Redis SCAN MATCH patterns. The /api/health/<name> endpoint attempted to resolve the supplied name to a known group or market, but when resolution failed it fell back to using the attacker-controlled value directly in a Redis key pattern. An unauthenticated attacker could therefore supply Redis glob metacharacters such as , ?, [ or ] to broaden the SCAN operation beyond the intended group. For example, requesting /api/health/ could enumerate health information, mirror slugs, and uptime series belonging to all groups and markets, including entities marked as private. Similar unsafe interpolation was present in /api/crypto/chain/<chain> and in the delete_manual_torrent() function. The latter represents a potentially destructive sink because a crafted infohash containing glob metacharacters could cause the scan to match torrent-health keys belonging to other torrents if attacker-controlled input can reach that function. The patch removes the unsafe fallback from the health endpoint and introduces glob escaping for user-controlled values before they are incorporated into Redis SCAN MATCH expressions.

Timeline

1. Aug 24, 2026, 1:19 PM UTCCVE published
2. Aug 24, 2026, 3:20 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Aug 24, 2026, 3:20 PM UTCRecord last updated

Affected versions

• ransomlook ransomlook

  through 2.0.0

References 1