{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32717 exists.","fix":"No fix has been published for CVE-2026-32717 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32717 is a low-severity authentication bypass vulnerability in Mintplexlabs Anythingllm, published on 13 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32717 and fix it if it is affected.\n\nWhat it is: CVE-2026-32717 is a low-severity authentication bypass vulnerability in Mintplexlabs Anythingllm, published on 13 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32717 exists.\n\nAffected product: Mintplexlabs Anythingllm. 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-32717/ (Markdown: https://insights.sbomify.com/CVE-2026-32717/index.md)","id":"CVE-2026-32717","markdown":"https://insights.sbomify.com/CVE-2026-32717/index.md","name":"CVE-2026-32717","record":{"aliases":["GHSA-7754-8jcc-2rg3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"AnythingLLM application","requires_auth":"high_privilege","summary":"Suspended users in multi-user mode can bypass access controls via browser extension API keys to read metadata and perform uploads.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"anythingllm","vendor":"mintplexlabs"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. In 1.11.1 and earlier, in multi-user mode, AnythingLLM blocks suspended users on the normal JWT-backed session path, but it does not block them on the browser extension API key path. If a user already has a valid brx-... browser extension API key, that key continues to work after suspension. As a result, a suspended user can still access browser extension endpoints, read reachable workspace metadata, and continue upload or embed operations even though normal authenticated requests are rejected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"AnythingLLM access control bypass: suspended users can continue using Browser Extension API keys","id":"CVE-2026-32717","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mintplexlabs:anythingllm","products":["mintplexlabs:anythingllm"],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Coolify read-scoped API tokens can perform state-changing validation operations","id":"CVE-2026-32718"},"packages":[],"prev":{"headline":"SciTokens: Authorization Bypass via Incorrect Scope Path Prefix Checking","id":"CVE-2026-32716"},"products":["anything-llm"],"published":"2026-03-13","related":[{"cvss_score":9.9,"headline":"Path Traversal in mintplex-labs/anything-llm","id":"CVE-2024-3025","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.9,"headline":"SSRF on AWS deployed instances of AnythingLLM via /metadata","id":"CVE-2024-0455","kev_date_added":null,"published":"2024-02-25"},{"cvss_score":9.7,"headline":"AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection","id":"CVE-2026-32626","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":9.6,"headline":"Remote Code Execution in mintplex-labs/anything-llm","id":"CVE-2024-3104","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.6,"headline":"SSRF in mintplex-labs/anything-llm","id":"CVE-2024-3149","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.6,"headline":"Default user role exporting save state of instance","id":"CVE-2024-0765","kev_date_added":null,"published":"2024-03-03"},{"cvss_score":9.6,"headline":"Privileged User using traversal to read system files","id":"CVE-2024-0550","kev_date_added":null,"published":"2024-02-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-16","vendors":["Mintplex-Labs"]},"summary":"Suspended users in multi-user mode can bypass access controls via browser extension API keys to read metadata and perform uploads.","url":"https://insights.sbomify.com/CVE-2026-32717/"}