dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-7844

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was detected in chatchat-space Langchain-Chatchat up to 0.3.1.3. This vulnerability affects the function files/list_files/retrieve_file/retrieve_file_content/delete_file of the file libs/chatchat-server/chatchat/server/api_server/openai_routes.py of the component Compatible File Service. The manipulation results in missing authentication. The attacker must have access to the local network to execute the attack. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Compatible File Service in Langchain-Chatchat up to version 0.3.1.3 lacks authentication on file management API endpoints (files/list_files/retrieve_file/retrieve_file_content/delete_file). Attackers with local network access can unauthenticatedy list, retrieve view, and delete files stored by the application.

MitigationImplement authentication checks on all file service API endpoints and restrict network access to the service until a patch is available from the vendor.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Langchain-Chatchat installation
    Check if Langchain-Chatchat is installed by searching for its package directory or running 'pip show langchain-chatchat' or checking common installation paths like /opt/langchain-chatchat, ~/langchain-chatchat, or in the Python environment.
    Affected if Langchain-Chatchat is installed on the system
  2. Determine the installed version
    Run 'pip show langchain-chatchat' or check the version in requirements.txt/setup.py if self-hosted. Compare the version against any known patched versions from the vendor.
    Affected if The installed version is older than the patched version (if known) or version cannot be determined
  3. Locate openai_routes.py file
    Find the openai_routes.py file in the Langchain-Chatchat installation directory, typically under the 'server/routes' or 'chatchat/server/routes' folder. Inspect the file for the functions: list_files, retrieve_file, retrieve_file_content, delete_file.
    Affected if The file exists and contains the four file operation functions without authentication decorators or checks
  4. Check if file service endpoints are network-accessible
    Review the application configuration (config.py, .env files, or startup parameters) to determine if the API server binds to 0.0.0.0 or a publicly accessible IP address, rather than localhost only.
    Affected if The service is bound to 0.0.0.0 or an exposed network interface rather than 127.0.0.1 only
  5. Verify authentication is not enforced on file endpoints
    Examine the openai_routes.py code or any middleware configuration to confirm whether authentication or authorization decorators are applied to the /files/* endpoints. Attempt a test request to these endpoints without credentials if testing in a non-production environment.
    Affected if No authentication middleware, decorators, or checks are present on the file operation endpoints

A user is affected if Langchain-Chatchat is installed and the Compatible File Service endpoints (list_files, retrieve_file, retrieve_file_content, delete_file) in openai_routes.py are network-accessible without any authentication mechanism enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authentication checks on all file service API endpoints and restrict network access to the service until a patch is available from the vendor.

Recommended fix Moderate confidence

Check Langchain-Chatchat GitHub releases for version > 0.3.1.3

  1. Check the official Langchain-Chatchat GitHub repository (github.com/chatchat-space/Langchain-Chatchat) for any security releases or patches addressing CVE-2026-7844
  2. If a newer version exists, upgrade to that version using: pip install langchain-chatchat --upgrade
  3. If no newer version is available, verify that the file service API endpoints (files/list_files/retrieve_file/retrieve_file_content/delete_file) in libs/chatchat-server/chatchat/server/api_server/openai_routes.py require authentication
  4. Implement authentication middleware for the Compatible File Service endpoints if not present
  5. Restart the chatchat-server service after applying changes
  6. Test that unauthenticated requests to file service endpoints are now rejected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7844 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data