CVE-2026-90562
8.1LangBot · LangBot
LangBot versions before 4.10.11 contain a password reset vulnerability due to insufficient entropy in recovery keys and a lack of rate limiting on the reset-password endpoint.
Executive summary
An unauthenticated remote attacker can reset the administrator password and gain full account access due to weak recovery key entropy and missing rate limiting in LangBot versions prior to 4.10.11.
Vulnerability
The application utilizes a cryptographically weak mechanism for password recovery keys, providing only 24 bits of entropy, and fails to implement rate limiting on the unauthenticated /api/v1/user/reset-password endpoint. This combination allows an unauthenticated attacker to perform brute force attacks to guess the recovery key and compromise administrative accounts.
Business impact
Successful exploitation results in a complete bypass of authentication, granting the attacker administrative control over the LangBot instance. Given the CVSS score of 8.1, this is a high-severity flaw that could lead to unauthorized data exfiltration, system reconfiguration, or complete loss of service. The potential for reputational damage and the compromise of sensitive organizational data necessitates immediate intervention.
Remediation
Immediate Action: Update LangBot to version 4.10.11 or later immediately to incorporate the necessary entropy improvements and rate limiting controls.
Proactive Monitoring: Review web server and application logs for high volumes of POST requests to the /api/v1/user/reset-password endpoint originating from single or distributed IP addresses.
Compensating Controls: Deploy a Web Application Firewall (WAF) to enforce strict rate limiting on the reset-password endpoint, effectively blocking automated attempts to guess the recovery key until the software can be patched.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
The vulnerability presents a significant risk of administrative account takeover. IT administrators should prioritize upgrading to version 4.10.11 as the primary method of remediation. If immediate patching is not feasible, implementing aggressive rate limiting via a WAF is essential to mitigate the risk of automated credential recovery attacks.
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section
Sources
Originally found and disclosed by George Chen, per the CVE Program record.