{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72917 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72917 is a medium-severity authentication bypass vulnerability in Mintplex-Labs anything-llm, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72917 and fix it if it is affected.\n\nWhat it is: CVE-2026-72917 is a medium-severity authentication bypass vulnerability in Mintplex-Labs anything-llm, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72917 in the wild and no public exploit code.\n\nAffected product: Mintplex-Labs anything-llm. 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-72917/ (Markdown: https://insights.sbomify.com/CVE-2026-72917/index.md)","id":"CVE-2026-72917","markdown":"https://insights.sbomify.com/CVE-2026-72917/index.md","name":"CVE-2026-72917","record":{"aliases":["GHSA-vv8w-wg6r-hq56","MINI-qcmw-w26w-632p"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"AnythingLLM application","requires_auth":"none","summary":"An attacker can bypass password recovery checks by submitting a single valid code twice with whitespace variations, leading to account takeover.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-180","name":"Incorrect Behavior Order: Validate Before Canonicalize"}],"description":"AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. From 1.0.0 to 1.15.0, AnythingLLM's unauthenticated account-recovery flow in server/utils/PasswordRecovery/index.js uses recoverAccount() to deduplicate the raw recoveryCodes values before trimming them, so one valid code submitted twice with different surrounding whitespace can satisfy the two-code check. Each normalized value can also match the same stored hash instead of consuming a distinct hash. An attacker who knows the target username and one recovery code can call POST /api/system/recover-account in multi-user mode, receive a password-reset token, and use POST /api/system/reset-password to take over the account, including an administrator account.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"AnythingLLM: Password recovery accepts one recovery code twice after whitespace normalization","id":"CVE-2026-72917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Rocket.Chat: Insecure implementation of websocket notifications","id":"CVE-2026-72918"},"packages":[],"prev":{"headline":"Mastodon: SSRF Protection Bypass via IPv4-compatible IPv6 Addresses","id":"CVE-2026-72916"},"products":["anything-llm"],"published":"2026-08-10","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":"partial"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["Mintplex-Labs"]},"summary":"An attacker can bypass password recovery checks by submitting a single valid code twice with whitespace variations, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-72917/"}