Unauthenticated file write and delete via upload traversal
Published Jun 30, 2026 · Updated Jun 30, 2026
Path traversal in OpenBMB ChatDev 2.2.0 and earlier allows remote attackers to write or delete host files through multipart uploads. AttachmentService.save_upload_file joins an unsanitized client filename to a temporary directory, then writes and unlinks the resulting path. An unauthenticated session identifier reaches the upload route, and filesystem permissions bound which server paths can be overwritten or deleted.
Summary
What happened
Path traversal in OpenBMB ChatDev 2.2.0 and earlier allows remote attackers to write or delete host files through multipart uploads. AttachmentService.save_upload_file joins an unsanitized client filename to a temporary directory, then writes and unlinks the resulting path. An unauthenticated session identifier reaches the upload route, and filesystem permissions bound which server paths can be overwritten or deleted.
The record
- CVE
- CVE-2026-58166
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- OpenBMB
- Product
- ChatDev
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record 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 <=2.2.0
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
- ChatDev traversal filename reproductionproof 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