CVE-2026-78551
Received Received - Intake

Authentication Timing Attack and Brute Force in RansomLook

Vulnerability report for CVE-2026-78551, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: CIRCL

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-25
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
ransomlook ransomlook *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-307 The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

RansomLook has multiple authentication weaknesses allowing unauthenticated remote attackers to enumerate valid usernames, perform unrestricted password guessing, and exhaust application resources. The login system previously checked username existence before password verification, causing faster responses for invalid usernames. Attackers could exploit timing differences to identify valid accounts. Additionally, the system lacked rate limiting, enabling brute-force attacks that consume CPU resources and cause denial of service.

Detection Guidance

Monitor login endpoint response times for timing discrepancies between valid and invalid usernames. Check for high CPU usage from repeated login attempts. Inspect logs for multiple failed login attempts from single IPs.

Impact Analysis

Attackers could exploit this to guess passwords for valid accounts, potentially gaining unauthorized access. The lack of rate limiting allows attackers to overload the system, causing service disruptions. Username enumeration could help attackers target specific accounts for further attacks like phishing or credential stuffing.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to insufficient authentication controls. The lack of rate limiting and username enumeration risks expose user accounts to brute-force attacks, potentially violating data protection requirements for access controls and security measures.

Mitigation Strategies
  • Implement rate limiting on login endpoints (5 attempts per 5 minutes per IP).
  • Ensure password verification runs for all login attempts, even invalid usernames.
  • Use Redis/Valkey to track failed attempts and block IPs after threshold.
  • Configure reverse proxy to trust X-Forwarded-For headers for accurate IP detection.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-78551. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart