RansomLook Login Endpoint Allows Timing-Based Username Enumeration and Unthrottled Authentication Attempts
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass, Denial of service
- Confidentiality · integrity · availability
- Low · None · High
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-307 and CWE-400.
Summary
RansomLook contains multiple weaknesses in its authentication endpoint that allow an unauthenticated remote attacker to enumerate valid usernames, perform unrestricted password-guessing attacks, and potentially exhaust application worker resources. For local authentication, the login implementation previously checked whether a submitted username existed before invoking the password hash verification function. Requests containing a nonexistent username therefore returned significantly faster than requests for valid accounts, for which the computationally expensive password verification routine was executed. A remote attacker could measure these response-time differences to determine which usernames correspond to valid RansomLook accounts. In addition, the /login endpoint did not restrict the number or frequency of failed authentication attempts. An attacker could consequently perform password brute-force, dictionary, password-spraying, or credential-stuffing attacks against known accounts without server-side throttling. For valid usernames, each authentication attempt also invokes the password key-derivation function, which consumes a significant amount of CPU time. A sufficiently high rate of login attempts could therefore occupy the application's synchronous Gunicorn workers and cause a denial of service affecting the entire application. The issue has been addressed by always performing password verification using a randomly generated dummy password hash when the supplied username does not exist, eliminating the username-dependent timing discrepancy. Failed authentication attempts are additionally rate-limited per client IP address using Valkey/Redis, with five failed attempts within five minutes resulting in a one-hour block. The reverse-proxy configuration was also updated so that the application derives the client address from a trusted X-Forwarded-For value that cannot be overridden by a client-supplied header.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| ransomlook | ransomlook | up to 2.0.0 | — | No fix listed | CNA |
- ransomlook Vendorransomlook Affected up to 2.0.0 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-78551
- 2026-10-03 Alias added: GHSA-vrw5-9j4x-chw5
- 2026-10-16 EPSS moved to the 50th–90th percentile
References
More ransomlook vulnerabilities
- TI-2026-54504 RansomLook Missing Authorization Allows Disclosure of Private Group and Ransom Note Data CVSS 4.0CRITICAL 9.2
- TI-2026-54503 RansomLook Unauthenticated Database Export Exposes Private Data CVSS 4.0CRITICAL 9.2
- TI-2026-54502 Missing Authentication Allows Unauthorized Creation of Crypto Groups in RansomLook CVSS 4.0HIGH 8.8
- TI-2026-54517 Stored Cross-Site Scripting via Untrusted Cryptocurrency Address Rendering in RansomLook CVSS 4.0HIGH 8.8
- TI-2026-54622 RansomLook API Key Disclosure Through /admin/apikeys HTML Source CVSS 4.0CRITICAL 9.4
- TI-2026-54516 RansomLook Missing Authorization in Web Configuration Editor Allows Application Configuration Modification CVSS 4.0CRITICAL 9.4
Sources
- CVE-2026-78551 · CVE Program
- CVE-2026-78551 · NVD
- FIRST EPSS
- GHSA-vrw5-9j4x-chw5 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences