CVE-2026-73431: its account activation · Vulnerability-Lookup Contains an Authentication Weakness
Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
AI-suggested
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.
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.