# CVE-2026-85671: QAnything 2.0.0 Unauthenticated Cross-User File Disclosure

> Unauthenticated attackers can bypass authentication to access and disclose cross-tenant knowledge base files and documents in QAnything.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-mq4x-r3rg-g5rq

## What is CVE-2026-85671?

CVE-2026-85671 is a high-severity authentication bypass vulnerability in netease-youdao QAnything, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

QAnything 2.0.0 contains an authentication bypass vulnerability in the /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc endpoints that allows unauthenticated attackers to access any uploaded file or document. Attackers can enumerate file identifiers through unauthenticated endpoints and retrieve base64-encoded files or parsed document chunks without ownership verification to disclose cross-tenant knowledge base content.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-85671?


## How do I fix CVE-2026-85671?

No fix has been published for CVE-2026-85671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85671 being exploited?

There is no known exploitation of CVE-2026-85671 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85671 and fix it if it is affected.

What it is: CVE-2026-85671 is a high-severity authentication bypass vulnerability in netease-youdao QAnything, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85671 in the wild and no public exploit code.

Affected product: netease-youdao QAnything. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85671/ (Markdown: https://insights.sbomify.com/CVE-2026-85671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85671
- OSV: https://osv.dev/vulnerability/CVE-2026-85671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85671/
Summaries are generated and may contain mistakes; the official description above is the record.