{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24477 exists.","fix":"No fix has been published for CVE-2026-24477 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24477 is a high-severity vulnerability in Mintplexlabs Anythingllm, published on 26 Jan 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-24477 and fix it if it is affected.\n\nWhat it is: CVE-2026-24477 is a high-severity vulnerability in Mintplexlabs Anythingllm, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24477 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-24477/ (Markdown: https://insights.sbomify.com/CVE-2026-24477/index.md)","id":"CVE-2026-24477","markdown":"https://insights.sbomify.com/CVE-2026-24477/index.md","name":"CVE-2026-24477","record":{"aliases":["GHSA-gm94-qc2p-xcwf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"AnythingLLM application","requires_auth":"none","summary":"Unauthenticated attackers can leak Qdrant API keys from the setup endpoint, gaining full read/write access to the vector database and confidential documents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"anythingllm","vendor":"mintplexlabs"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. If AnythingLLM prior to version 1.10.0 is configured to use Qdrant as the vector database with an API key, this QdrantApiKey could be exposed in plain text to unauthenticated users via the `/api/setup-complete` endpoint. Leakage of QdrantApiKey allows an unauthenticated attacker full read/write access to the Qdrant vector database instance used by AnythingLLM. Since Qdrant often stores the core knowledge base for RAG in AnythingLLM, this can lead to complete compromise of the semantic search / retrieval functionality and indirect leakage of confidential uploaded documents. Version 1.10.0 patches the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-24477.yaml","stars":null,"title":"AnythingLLM - Information Disclosure"}],"tier":"weaponised"},"has_fix":false,"headline":"AnythingLLM has key leak in `systemSettings.js`","id":"CVE-2026-24477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mintplexlabs:anythingllm","products":["mintplexlabs:anythingllm"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"AnythingLLM vulnerable to Path Traversal","id":"CVE-2026-24478"},"packages":[],"prev":{"headline":"Shaarli vulnerable to stored XSS via Suggested Tags","id":"CVE-2026-24476"},"products":["anything-llm"],"published":"2026-01-26","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-03","vendors":["Mintplex-Labs"]},"summary":"Unauthenticated attackers can leak Qdrant API keys from the setup endpoint, gaining full read/write access to the vector database and confidential documents.","url":"https://insights.sbomify.com/CVE-2026-24477/"}