CVE-2026-58166: OpenBMB ChatDev: unauthenticated path traversal in file upload
OpenBMB ChatDev through 2.2.0 contains a path traversal flaw (CWE-22) in its upload handling, where the destination path is built from the multipart filename without sanitization. The record states that unauthenticated remote actors can write or delete arbitrary files on the server, and that the issue is fixed in commit 4fd4da6. No confirmed exploitation in the wild appears in the sources consulted.
Overview
OpenBMB ChatDev through 2.2.0 contains a path traversal weakness (CWE-22) in its file upload handling. According to the record, the POST uploads session endpoint builds the destination path from the multipart filename without sanitization inside save_upload_file, so file write and cleanup operations can target paths chosen by the sender. The record states the issue is fixed in commit 4fd4da6.
Impact
- The record states that unauthenticated remote actors can write or delete arbitrary files on the server filesystem.
- The CVSS 3.1 score of 9.1 in the record is provided by VulnCheck; its vector rates integrity and availability impact as high and confidentiality impact as none.
- The record also lists a CVSS 4.0 score of 8.8 from VulnCheck.
- Based on the stated scope, the main risks are integrity loss, service disruption through deletion of files, and possible follow-on compromise, which is an inference.
Affected products and versions
- Product: OpenBMB ChatDev.
- Versions: the description states 'through 2.2.0'.
- The structured affected list in the record is empty, so exact range boundaries cannot be confirmed from structured data.
- The record identifies the fix as commit 4fd4da6. No fixed release version appears in the record.
Exploitation status
- CISA KEV does not list this CVE in the record.
- No confirmed exploitation in the wild appears in the sources consulted.
- EPSS probability is 0.00854 with percentile 0.57209, dated 2026-10-13.
Remediation and mitigation
- Update ChatDev to a code state that includes commit 4fd4da6 or later. Check the upstream repository for the first release that contains this commit.
- Until the fix is applied, limit network exposure of the ChatDev service, restrict access to trusted networks, and place it behind an authentication layer.
- Run the service with the minimum filesystem write permissions needed, and keep sensitive files outside directories it can modify.
- Back up the upload directory and application configuration so that unexpected deletions can be recovered.
Detection guidance
- Review web server and application logs for requests to the uploads session endpoint from unexpected sources or with unusual filename values.
- Monitor file integrity on the host, with attention to changes or deletions outside the expected upload directory.
- Alert on unexpected modification or removal of application code and configuration files.
Limitations of the available information
- The record contains no structured affected or fixed version data.
- The contents of the GitHub pull request and issue listed in the references are not included in the record.
- The VulnCheck advisory is listed as a reference, but its text is not included in the record.
- No NVD CVSS score appears in the record; the scores shown come from VulnCheck.
- The source status is recorded as Deferred.
Frequently asked questions
What does CVE-2026-58166 affect?
The record describes OpenBMB ChatDev through 2.2.0. The structured affected list is empty, so exact version boundaries are not confirmed by structured data.
Does the record show a fixed version?
The record identifies a fix in commit 4fd4da6 but does not list a fixed release version. Check the upstream repository for the release that includes that commit.
Is this vulnerability being actively exploited?
CISA KEV does not list it in the record, and no confirmed exploitation in the wild appears in the sources consulted.
What is the severity?
VulnCheck provides a CVSS 3.1 score of 9.1 and a CVSS 4.0 score of 8.8 in the record. No NVD score appears in the record.
This analysis was drafted with AI assistance from verified source data and automatically checked against it.