CVE-2025-6854VulnerabilityPublished 29 Jun 2025Updated 30 Jun 2025

CVE-2025-6854: Langchain-Chatchat · Path Traversal

Affects Langchain-ChatchatSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubchatchat-space/Langchain-Chatchat`pkg:github/chatchat-space/Langchain-Chatchat`Other threats	Affected =0.3.0 =0.3.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should include restricting external access to the /v1/files?purpose=assistants endpoint by implementing network-level controls such as firewalls or VPNs to limit access to trusted internal users only. 2. Employ web application firewalls (WAFs) with custom rules to detect and block path traversal patterns (e.g., ../ sequences) in HTTP requests targeting the vulnerable endpoint. 3. Conduct input validation and sanitization on all file path parameters to reject or canonicalize suspicious inputs before processing. 4. Monitor logs for unusual access patterns or attempts to exploit path traversal, enabling rapid detection and response. 5. If possible, isolate the Langchain-Chatchat service in a container or sandbox environment with minimal file system permissions to limit the impact of any successful traversal. 6. Engage with the vendor or open-source maintainers to obtain patches or updates addressing this vulnerability as soon as they become available. 7. Review and audit deployment configurations to ensure that sensitive files are not stored in locations accessible by the application. 8. Educate development and operations teams about secure coding and deployment practices to prevent similar vulnerabilities in future versions.

Description

A vulnerability classified as problematic was found in chatchat-space Langchain-Chatchat up to 0.3.1. This vulnerability affects unknown code of the file /v1/files?purpose=assistants. The manipulation leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using Langchain-Chatchat versions 0.3.0 or 0.3.1, this vulnerability poses a risk of unauthorized data disclosure through path traversal attacks. Sensitive files on the server may be exposed, including configuration files, credentials, or user data processed by the AI assistant framework. This could lead to privacy violations under GDPR if personal data is accessed or leaked. The medium severity rating reflects moderate risk: while attackers cannot modify or delete data, the confidentiality breach alone can have regulatory and reputational consequences. Organizations in sectors such as finance, healthcare, and government, which often handle sensitive information and may deploy AI assistants, are particularly at risk. The remote and unauthenticated nature of the attack increases the likelihood of exploitation if the vulnerable service is internet-facing. Additionally, the public disclosure of the exploit details raises the urgency for European entities to assess and mitigate exposure. The impact on availability and integrity is minimal, so service disruption or data tampering is unlikely. However, the potential for data leakage and compliance violations makes this a significant concern for European organizations relying on this software.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jun 2025, 09:09 UTC

Technical details

References

Community reviews

Related threats