{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-73431 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-73431 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73431 is a high-severity vulnerability in vulnerability-lookup, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73431 and fix it if it is affected.\n\nWhat it is: CVE-2026-73431 is a high-severity vulnerability in vulnerability-lookup, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-73431 in the wild and no public exploit code.\n\nAffected product: vulnerability-lookup. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73431/ (Markdown: https://insights.sbomify.com/CVE-2026-73431/index.md)","id":"CVE-2026-73431","markdown":"https://insights.sbomify.com/CVE-2026-73431/index.md","name":"CVE-2026-73431","record":{"aliases":["GHSA-w4vj-gm7w-293h"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Vulnerability Lookup","requires_auth":"low_privilege","summary":"Attackers can repeatedly take over accounts by replaying captured activation or recovery tokens because the application fails to invalidate them after use.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"Vulnerability-Lookup contains an \nauthentication weakness in its account activation and password-recovery \nmechanism. Activation and recovery links were generated using stateless \nsigned tokens containing only the user's login. Although the token \nsignature and age were validated, the application did not track whether a\n token had already been successfully used. As a result, a captured \nactivation or password-recovery link remained valid for the entire \nconfigured TOKEN_VALIDITY_PERIOD, even after the associated password had been changed. \n\nAn attacker who obtains a valid \nactivation or recovery token could therefore replay it multiple times \nduring its validity period to set a new password and repeatedly take \ncontrol of the affected account. In addition, tokens were not bound to a\n specific purpose, allowing the same token mechanism to be used across \nactivation and recovery workflows. The patch introduces purpose-bound \ntokens and a random nonce whose SHA-256 digest is stored with the user \naccount. The nonce is invalidated after a successful password change, \nmaking tokens single-use, while issuing a new token invalidates any \npreviously issued token.  The password-setting operation now explicitly consumes the token before committing the account change. \n\nSuccessful exploitation requires \nthe attacker to obtain a currently valid activation or recovery link, \nbut does not require knowledge of the victim's existing password or an \nauthenticated session.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Reusable Account Activation and Recovery Tokens Allow Repeated Account Takeover in vulnerability-lookup","id":"CVE-2026-73431","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in vulnerability-lookup","id":"CVE-2026-73432"},"packages":[],"prev":{"headline":"Russh: Pre-auth remote panic via all-zero Curve25519 peer public value (encode_mpint OOB)","id":"CVE-2026-73430"},"products":["vulnerability-lookup"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["vulnerability-lookup"]},"summary":"Attackers can repeatedly take over accounts by replaying captured activation or recovery tokens because the application fails to invalidate them after use.","url":"https://insights.sbomify.com/CVE-2026-73431/"}