CVE-2026-101041
MediumCVSS 6.3Exploitation Probability (EPSS)
Low risk12th percentile - higher than 12% of all known CVEs
Summary
The account recovery (password reset) functionality in the vulnerability-lookup web application contains a TOCTOU race condition in the consumption of single-use recovery tokens. Two concurrent HTTP requests with the same valid token can both pass verification before either transaction commits, allowing both to set their own password on the target account. Additionally, a secondary defect in the same endpoint allows a valid recovery link to set an empty or trivially short password because form validation is not invoked.
Risk Assessment
An attacker with a valid recovery token can take over a user's account by changing the password, potentially leading to unauthorized access to sensitive data. The ability to set weak passwords increases the risk of subsequent compromise.
Recommendation
Update the vulnerability-lookup application to a version that fixes the TOCTOU race and enforces password validation. Additionally, consider implementing mechanisms to block concurrent token use and require strong passwords.
Other vulnerabilities in vulnerability-lookup
See all- CVE-2026-73432Medium
SSRF vulnerability in the remote-instance synchronization functionality of Vulnerability-Lookup. Remote instance addresses were validated only for basic URL syntax before being stored, and the synchronization worker later dereferenced them without network-boundary restrictions, following redirects without revalidation. An authenticated administrator with admin:access permission could configure a remote instance pointing to internal, loopback, link-local, or cloud metadata services.
- CVE-2026-73431High
Vulnerability-Lookup has an authentication weakness in account activation and password recovery, where tokens are reusable and not purpose-bound. An attacker who obtains a valid link can repeatedly change the password and take control of the account.
- CVE-2026-73405Medium
An authorization bypass vulnerability in Vulnerability-Lookup allowed inactive or unconfirmed accounts to subscribe to Server-Sent Events (SSE) streams through the /pubsub/subscribe/<topic> endpoint. The token_required decorator only checked the X-API-KEY header against an existing user API key, without verifying the account's is_active and is_confirmed state. An attacker could create an account and immediately use the API key to access Pub/Sub topics that should only be available to active, confirmed users.
- CVE-2026-73374Medium
A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference tags associated with vulnerability records. Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and wrapped in markupsafe.Markup, bypassing Jinja's automatic HTML escaping. An authenticated user with permissions to create or modify vulnerability records could submit a crafted reference tag through the CNA API containing arbitrary HTML or JavaScript-capable markup.
- CVE-2025-60249Medium
vulnerability-lookup 2.16.0 contains an XSS vulnerability in bundle.py, comment.py, and user.py, which can be exploited by a user of a vulnerability-lookup instance who can add bundles, comments, or sightings. The vulnerability stems from insufficient sanitization of user-supplied input before rendering in templates and tables, allowing injection of arbitrary JavaScript.
Original NVD description (English source)
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).
Vulnerability data from NVD (NIST) · CISA KEV · EPSS