Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessTrigger or observe password-recovery request for target account
-
DeliveryIntercept or obtain recovery link from victim's email channel
-
ExploitSubmit token URL to set attacker-controlled password
-
ExecutionAuthenticate as victim with new credentials
-
ImpactReplay same token to maintain control if victim self-recovers
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Replay attack prevention
|
| Exploitation Conditions | Exploitation requires the attacker to possess a currently valid, unexpired account activation or password-recovery token URL for the target account - specifically a link generated by Vulnerability-Lookup's activation or recovery workflow and still within the configured TOKEN_VALIDITY_PERIOD. The token must have been generated, meaning the victim or the attacker must have already triggered an activation or recovery request for the target account. No knowledge of the victim's existing password is required, and no authenticated session on the platform is needed. Limiting factors: the attacker must obtain the token URL through an out-of-band channel such as email interception or phishing; the token expires once TOKEN_VALIDITY_PERIOD elapses; and only accounts that have an outstanding activation or recovery request are directly exposed at any given moment. |
| Impact | The provided CVSS 4.0 score of 8.8 (AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N) reflects network-exploitable account takeover with high impact on both the vulnerable system and subsequent systems - the latter plausible given Vulnerability-Lookup's role as a threat intelligence platform where account compromise could expose or manipulate sensitive CVE data downstream. AC:H correctly signals that exploitation is not trivially automated: the attacker must first capture a valid token in transit, requiring email interception, phishing, or similar means. PR:L in the provided vector likely reflects that the token itself functions as a constrained credential, though the attacker need not hold an active authenticated session on the platform. No EPSS score was provided; exploitation probability is therefore not quantifiable from available data. No CISA KEV listing exists and no public POC exploit is identified, placing real-world risk in the targeted rather than widespread category. The most credible threat actor is one with access to the victim's email channel, making this a meaningful risk for high-value accounts but not a mass-exploitation scenario. |
| Exploit ScenarioDerived | An attacker targets a Vulnerability-Lookup user who recently requested a password reset and intercepts the recovery email - via a compromised mail server, a shared inbox, or by tricking the user into forwarding the link. The attacker submits the token URL to set a new password and gain full account access, then replays the same link repeatedly during the TOKEN_VALIDITY_PERIOD to regain control even after the legitimate user attempts to recover their account using the same link. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 12, 2026
Token replay in Vulnerability-Lookup's account activation and password-recovery mechanism allows an attacker who captures a valid one-time link to repeatedly reset the victim's password throughout the entire TOKEN_VALIDITY_PERIOD, even after the legitimate user has already consumed that token. Because the application never records whether a token has been used and does not bind tokens to a specific workflow, a single intercepted link grants persistent account-takeover capability without requiring any knowledge of the victim's current credentials. Reported by CIRCL, no public exploit code or CISA KEV listing exists at time of analysis; an upstream patch is available via a GitHub commit.
RemediationAI
The primary fix is to update Vulnerability-Lookup to the version incorporating commit bef837242657acf680832be56b94428df130ed67, available at https://github.com/vulnerability-lookup/vulnerability-lookup/commit/bef837242657acf680832be56b94428df130ed67; no independently confirmed patched release version number is available at time of analysis. As a compensating control pending upgrade, administrators should reduce TOKEN_VALIDITY_PERIOD to the minimum operationally acceptable value to shrink the replay window - note that an overly short window may cause legitimate users to miss their activation or recovery links and require re-issuance. Enabling email delivery logging and alerting on duplicate token submission attempts for the same account can aid detection. Forcing all currently outstanding activation and recovery tokens to expire by rotating the token signing secret will immediately invalidate any tokens captured by an attacker, though this will also invalidate tokens in legitimate users' inboxes, requiring those users to re-request links.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Vulnerability-Lookup (cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*) is a CIRCL-maintained web platform for aggregating and querying vulnerability intelligence. The root cause is CWE-294 (Authentication Bypass by Capture-replay): the application issued stateless signed tokens encoding only the user's login for both account activation and password-recovery flows. Signature validity and token age were checked, but no server-side record of token consumption was maintained, allowing unlimited replays within the TOKEN_VALIDITY_PERIOD window. Tokens were additionally not purpose-scoped, permitting a recovery token to be reused in an activation context and vice versa. The patch commit (bef837242657acf680832be56b94428df130ed67) resolves both issues by introducing purpose-bound tokens, a random nonce whose SHA-256 digest is stored per user account, and explicit token consumption before committing any account change - making each token single-use and invalidating outstanding tokens when a new one is issued. The accompanying change to pubsub.py adds active/confirmed account-state gates on the pub/sub subscription endpoint, closing a secondary path where a pre-confirmation key could subscribe to pre-moderation data.
Know when Vulnerability Lookup gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Network-exploitable token replay requiring no authenticated session (PR:N) but AC:H because capturing a valid in-flight token is a necessary precondition; no availability impact applies.
Primary rating from Vendor (CIRCL).
CVSS VectorVendor: CIRCL
DescriptionCVE.org
Vulnerability-Lookup contains an authentication weakness in its account activation and password-recovery mechanism. Activation and recovery links were generated using stateless signed tokens containing only the user's login. Although the token signature and age were validated, the application did not track whether a token had already been successfully used. As a result, a captured activation or password-recovery link remained valid for the entire configured TOKEN_VALIDITY_PERIOD, even after the associated password had been changed.
An attacker who obtains a valid activation or recovery token could therefore replay it multiple times during its validity period to set a new password and repeatedly take control of the affected account. In addition, tokens were not bound to a specific purpose, allowing the same token mechanism to be used across activation and recovery workflows. The patch introduces purpose-bound tokens and a random nonce whose SHA-256 digest is stored with the user account. The nonce is invalidated after a successful password change, making tokens single-use, while issuing a new token invalidates any previously issued token. The password-setting operation now explicitly consumes the token before committing the account change.
Successful exploitation requires the attacker to obtain a currently valid activation or recovery link, but does not require knowledge of the victim's existing password or an authenticated session.
Executive ViewAI
Vulnerability-Lookup (CVE-2026-73431, CVSS 8.8) contains an authentication bypass in its password-recovery mechanism that allows attackers to permanently compromise any user account by intercepting a single password-reset link. Attackers can reset victims' passwords repeatedly without knowing current credentials, maintaining access throughout the token validity period and creating indefinite account takeover risk that could expose sensitive data and compromise platform operations.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Vulnerability Lookup
View allSSRF guard bypass in Vulnerability Lookup's webhook notification subsystem allows a network attacker to register a webho
Time-of-check-to-time-of-use race condition in the account recovery endpoint of vulnerability-lookup (/user/confirm_acco
Stored cross-site scripting in Vulnerability-Lookup's render_tag_badges Jinja filter allows an authenticated user holdin
Inconsistent authorization enforcement in Vulnerability-Lookup's SSE streaming interface allows self-registered but unco
Server-side request forgery in Vulnerability-Lookup's remote-instance synchronization feature enables an authenticated a
EUVD-2026-57226
GHSA-w4vj-gm7w-293h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB