vulnerability-lookup up to 6.2.0 Account Recovery website/models/user.py toctou

Summaryinfo

A vulnerability identified as critical has been detected in vulnerability-lookup up to 6.2.0. This issue affects some unknown processing of the file website/models/user.py of the component Account Recovery. The manipulation leads to toctou. This vulnerability is traded as CVE-2026-101041. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in vulnerability-lookup up to 6.2.0 and classified as critical. This issue affects some unknown functionality of the file website/models/user.py of the component Account Recovery. The manipulation with an unknown input leads to a toctou vulnerability. Using CWE to declare the problem leads to CWE-367. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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).

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-101041 since 09/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• vulnerability-lookup

Version

• 6.0
• 6.1
• 6.2.0

Website

• Product: https://github.com/vulnerability-lookup/vulnerability-lookup/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion