Arbitrary file write via unsanitized upload filename
Published Jun 29, 2025 · Updated Jun 30, 2025
Path traversal in Chatchat-Space Langchain-Chatchat 0.3.1 and earlier allows remote attackers to write arbitrary files. The /v1/files handler passes the uploaded filename through _get_file_id and _get_file_path, then opens the resulting path for writing without verifying that it remains under the upload directory. A crafted multipart filename can overwrite files writable by the service account; remote exposure requires changing the default loopback bind address.
Summary
What happened
Path traversal in Chatchat-Space Langchain-Chatchat 0.3.1 and earlier allows remote attackers to write arbitrary files. The /v1/files handler passes the uploaded filename through _get_file_id and _get_file_path, then opens the resulting path for writing without verifying that it remains under the upload directory. A crafted multipart filename can overwrite files writable by the service account; remote exposure requires changing the default loopback bind address.
The record
- CVE
- CVE-2025-6855
- Published
- Jun 29, 2025
- Updated
- Jun 30, 2025
- Vendor
- Chatchat-Space
- Product
- Langchain-Chatchat
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.3.0
- Affected versionversion=0.3.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream /v1/files traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo