CVE-2026-35393
Directory Traversal in goshs POST Multipart Upload Pre-2.0.0-beta
Publication date: 2026-04-06
Last updated on: 2026-04-09
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| goshs | goshs | 2.0.0 |
| goshs | goshs | to 2.0.0 (exc) |
| goshs | goshs | 2.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in goshs, a SimpleHTTPServer written in Go, where prior to version 2.0.0-beta.3, the POST multipart upload directory was not sanitized. This means that when files were uploaded via POST requests, the directory paths were not properly checked or cleaned, potentially allowing malicious input to affect the server.
How can this vulnerability impact me? :
This vulnerability can have a severe impact as indicated by its high CVSS score of 9.8. Because the upload directory is not sanitized, an attacker could exploit this to compromise the confidentiality, integrity, and availability of the system. This could lead to unauthorized access, data corruption, or denial of service.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade goshs to version 2.0.0-beta.3 or later, where the POST multipart upload directory sanitization issue is fixed.