CVE-2026-101041
Vulnerability-Lookup - Race Condition in Account Recovery Token Consumption Allows Password Takeover
The account recovery (password reset) functionality in the vulnerability-lookup web application contains a time-of-check-to-time-of-use (TOCTOU) race condition in the consumption of single-use recovery tokens. The original implementation verified the token nonce against the stored digest and then consumed (cleared) it in separate database operations. Two concurrent HTTP requests presenting the same valid recovery token could both pass the verification check before either transaction committed, allowing both to set their own password on the target account. The last transaction to commit overwrites the first, enabling an attacker who possesses a valid recovery token to replace the legitimate user's password with one of their choosing. A secondary defect in the same endpoint (confirm_account) allowed a valid recovery link to be used to set an empty or trivially short password (e.g., three characters). The view handler performed only a manual equality comparison between the two password fields and never invoked the form's validation logic, bypassing the intended minimum-length and complexity constraints. The affected component is the user account recovery endpoint (/user/confirm_account/<token>) and the associated token verification and consumption logic in the User model (website/models/user.py) and the view layer (website/web/views/user.py).
| CWE | CWE-362 CWE-20 |
| Vendor | vulnerability-lookup |
| Product | vulnerability-lookup |
| Published | Sep 27, 2026 |
Get instant alerts for vulnerability-lookup vulnerability-lookup
Be the first to know when new unknown vulnerabilities affecting vulnerability-lookup vulnerability-lookup are published β delivered to Slack, Telegram or Discord.