Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-85671 – Unauthenticated File & Document Disclosure – QAnything ≤ 2.0.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85671 is a missing authentication vulnerability (CWE-306) affecting QAnything, the open-source retrieval-augmented Q&A/knowledge-base platform from NetEase Youdao. The /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc endpoints do not enforce authentication or ownership checks, allowing a remote, unauthenticated attacker to retrieve base64-encoded files and parsed document chunks belonging to any tenant. The issue carries a High severity rating (CVSS 8.7) and directly threatens the confidentiality of knowledge-base content stored in affected deployments.

Technical details

  • Root cause: The get_file_base64 and get_doc handlers in QAnything’s local_doc_qa API do not validate that the requesting user/session is authorized to access the requested file or document identifier — no authentication or ownership/tenant verification is performed before returning content.
  • Trigger conditions: An attacker only needs network access to the exposed API and a valid or guessable/enumerable file or document ID; no credentials, session tokens, or user interaction are required.
  • Attack vector: Network-based (AV:N), low attack complexity, no privileges required, no user interaction — the attacker sends direct HTTP requests to the affected endpoints.
  • Impact: Disclosure of arbitrary uploaded files (via base64 retrieval) and parsed document chunks across knowledge bases, including cross-tenant data in multi-tenant deployments. The vulnerability impacts confidentiality only; integrity and availability are not affected.

Affected software

  • Product: QAnything (netease-youdao/QAnything)
  • Versions affected: All versions up to and including 2.0.0

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 8.7 (High) — 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

Mitigation and recommended actions

  • Immediate: At the time of publication, no patched release addressing this specific issue has been confirmed. Organizations should monitor the official NetEase Youdao QAnything repository for a fixed release beyond 2.0.0 and upgrade as soon as a patch is available.
  • If no patch is available:
    • Do not expose QAnything’s API endpoints (particularly /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc) directly to the internet.
    • Place the application behind an authenticating reverse proxy or API gateway that enforces access control and ownership checks before requests reach these endpoints.
    • Restrict network access to trusted internal networks or VPN, and apply firewall rules/allow-lists limiting who can reach the QAnything service.
    • Audit file and document identifiers for predictability; where possible, rotate or randomize identifiers to reduce the risk of enumeration.
    • Monitor access logs for unusual or high-volume requests to the affected endpoints, which may indicate enumeration attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge