Vulnerability-Lookup contains an authentication weakness in its account activation and password-recovery mechanism. (CVE-2026-73431)
Vulnerability-Lookup has an authentication weakness in its account activation and password-recovery mechanism. Stateless signed tokens containing only the user's login were used for activation and recovery links. These tokens remained valid for the entire configured validity period even after password changes, allowing replay attacks. Tokens were also not bound to specific purposes, enabling reuse across workflows. The vulnerability allows an attacker who obtains a valid token to repeatedly reset the password and take control of the account without needing the victim's password or an authenticated session.
AI Analysis
Technical Summary
The vulnerability in Vulnerability-Lookup involves the use of stateless signed tokens for account activation and password recovery that only include the user's login. Although token signature and age were validated, the system did not track token usage, allowing replay of valid tokens multiple times within their validity period. Tokens were not purpose-bound, permitting the same token to be used for both activation and recovery workflows. This flaw enables an attacker who obtains a valid token to repeatedly reset the password and take control of the account. The patch introduces purpose-bound tokens with a random nonce stored as a SHA-256 digest linked to the user account. The nonce is invalidated after a successful password change, making tokens single-use and invalidating previous tokens upon new issuance. Password changes now explicitly consume the token before committing changes.
Potential Impact
An attacker who obtains a valid activation or password-recovery token can repeatedly reset the password and take control of the affected account during the token's validity period. This does not require knowledge of the victim's existing password or an authenticated session, significantly increasing the risk of account takeover.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described patch introduces purpose-bound tokens and nonce invalidation to prevent token reuse. Until a patch is applied, restrict access to activation and recovery links and monitor for suspicious token usage if possible.
Vulnerability-Lookup contains an authentication weakness in its account activation and password-recovery mechanism. (CVE-2026-73431)
Description
Vulnerability-Lookup has an authentication weakness in its account activation and password-recovery mechanism. Stateless signed tokens containing only the user's login were used for activation and recovery links. These tokens remained valid for the entire configured validity period even after password changes, allowing replay attacks. Tokens were also not bound to specific purposes, enabling reuse across workflows. The vulnerability allows an attacker who obtains a valid token to repeatedly reset the password and take control of the account without needing the victim's password or an authenticated session.
CVSS v4.0
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Vulnerability-Lookup involves the use of stateless signed tokens for account activation and password recovery that only include the user's login. Although token signature and age were validated, the system did not track token usage, allowing replay of valid tokens multiple times within their validity period. Tokens were not purpose-bound, permitting the same token to be used for both activation and recovery workflows. This flaw enables an attacker who obtains a valid token to repeatedly reset the password and take control of the account. The patch introduces purpose-bound tokens with a random nonce stored as a SHA-256 digest linked to the user account. The nonce is invalidated after a successful password change, making tokens single-use and invalidating previous tokens upon new issuance. Password changes now explicitly consume the token before committing changes.
Potential Impact
An attacker who obtains a valid activation or password-recovery token can repeatedly reset the password and take control of the affected account during the token's validity period. This does not require knowledge of the victim's existing password or an authenticated session, significantly increasing the risk of account takeover.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described patch introduces purpose-bound tokens and nonce invalidation to prevent token reuse. Until a patch is applied, restrict access to activation and recovery links and monitor for suspicious token usage if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w4vj-gm7w-293h
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-73431"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a7c9b1abf8831d539cda0de
Added to database: 08/12/2026, 16:11:06 UTC
Last enriched: 08/12/2026, 16:13:25 UTC
Last updated: 08/13/2026, 01:41:08 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.