CVE-2026-85671

QAnything 2.0.0 fails to require authentication on the /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc API endpoints (CWE-306), allowing any unauthenticated attacker to invoke them remotely. Because these endpoints perform no ownership verification, an attacker can first enumerate file and document identifiers through unauthenticated interfaces and then retrieve base64-encoded file contents or parsed document chunks belonging to other tenants' knowledge bases. The impact is confidentiality-only — cross-tenant disclosure of uploaded files and indexed document content — with no integrity or availability consequences. Any QAnything 2.0.0 deployment is affected, with internet-exposed or multi-tenant instances facing the greatest risk. No public proof-of-concept, in-the-wild exploitation, or KEV listing is known, and EPSS currently estimates only a 0.4% probability of exploitation within 30 days.

What to do: Upgrade QAnything to a patched release as soon as the vendor publishes one (no fixed version is stated in current disclosures). As interim mitigation, block or restrict /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc to authenticated requests via a reverse proxy or firewall, reduce internet exposure of the QAnything API, and review access logs for unauthenticated requests to these endpoints.