CVE-2026-7844
Missing Authentication in Langchain-Chatchat File Service
Publication date: 2026-05-05
Last updated on: 2026-05-05
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chatchat | langchain-chatchat | to 0.3.1.3 (inc) |
| chatchat-space | langchain-chatchat | to 0.3.1.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-7844 is a vulnerability in Langchain-Chatchat (up to version 0.3.1.3) affecting the file service endpoints under /v1/files. These endpoints, which handle file upload, listing, retrieval, and deletion, lack proper authentication and authorization checks. This means that anyone with access to the local network can interact with these file operations without needing to log in or prove their identity.
The vulnerability is worsened by predictable file identifiers, overly permissive CORS settings that allow all origins, and the default configuration binding the API to all network interfaces (0.0.0.0), which exposes the service broadly on the local network.
As a result, an attacker can upload, list, read, or delete files belonging to any user without authentication, potentially accessing sensitive information or disrupting file availability.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive files, modification or deletion of files, and disruption of services relying on these files.
- Confidentiality risk: Attackers can read sensitive files such as screenshots or documents.
- Integrity risk: Files can be modified or deleted by unauthorized users.
- Availability risk: Deletion of files can disrupt ongoing services or workflows.
The vulnerability can be exploited remotely if the API port (default 7861) is exposed to untrusted networks, increasing the risk of attack beyond just local network users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the Langchain-Chatchat API port (default 7861) is exposed on your local network without authentication on the /v1/files endpoints.
You can attempt to access the file service endpoints to see if they respond without requiring authentication. For example, using curl commands to list files or retrieve file content can help detect the vulnerability.
- curl http://<target-ip>:7861/v1/files -v
- curl http://<target-ip>:7861/v1/files/<file_id> -v
- curl http://<target-ip>:7861/v1/files/<file_id>/content -v
- curl -X DELETE http://<target-ip>:7861/v1/files/<file_id> -v
If these commands succeed without authentication, it indicates the presence of the missing authentication vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable API port (default 7861) to trusted hosts only, such as by using firewall rules or network segmentation.
Additionally, it is recommended to add authentication middleware to the /v1/files endpoints to enforce proper authorization checks.
Validate file ownership to ensure users can only access their own files.
Tighten CORS settings by restricting allowed origins instead of permitting all origins.
Avoid default Docker configurations that bind the API service to all network interfaces (0.0.0.0) or use network_mode: host, which exposes the port to the LAN.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Langchain-Chatchat allows unauthenticated attackers on the local network to access, read, modify, or delete files without authorization. This leads to high confidentiality and integrity risks, as sensitive files such as screenshots or documents can be exposed or altered.
Such unauthorized access and potential data breaches can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require strict controls on data confidentiality, integrity, and access authorization.
Specifically, the lack of authentication and overly permissive CORS settings increase the risk of unauthorized data exposure, which can result in violations of data protection requirements mandated by these regulations.
Mitigation steps recommended include adding authentication middleware, validating file ownership, and restricting CORS to trusted origins, which are necessary to help maintain compliance with such standards.