# CVE-2026-35392: goshs has an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in goshs PUT Upload

> Attackers can upload arbitrary files via path traversal in goshs PUT requests, potentially leading to code execution or data modification.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-g8mv-vp7j-qp64, GO-2026-5394

## What is CVE-2026-35392?

CVE-2026-35392 is a critical path traversal vulnerability in patrickhener goshs, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

goshs is a SimpleHTTPServer written in Go. Prior to 2.0.0-beta.3, PUT upload in httpserver/updown.go has no path sanitization. This vulnerability is fixed in 2.0.0-beta.3.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-35392?

3 open source packages ship an affected version, including github.com/patrickhener/goshs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/patrickhener/goshs` | Go | All versions | 1.1.5-0.20260401172448-237f3af891a9 |
| `github.com/patrickhener/goshs` | Go | All versions | 1.1.5-0.20260401172448-237f3af891a9 |
| `github.com/patrickhener/goshs` | Go | All versions | 1.1.5-0.20260401172448-237f3af891a9 |

Products: Goshs Goshs.

## How do I fix CVE-2026-35392?

Upgrade github.com/patrickhener/goshs to 1.1.5-0.20260401172448-237f3af891a9 or later.

## Is CVE-2026-35392 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35392 exists.

## Other vulnerabilities in patrickhener goshs

- [CVE-2026-40884](https://insights.sbomify.com/CVE-2026-40884/): goshs: Empty-username SFTP password authentication bypass in goshs (critical 9.8)
- [CVE-2026-35393](https://insights.sbomify.com/CVE-2026-35393/): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in goshs POST multipart upload (critical 9.8)
- [CVE-2026-35471](https://insights.sbomify.com/CVE-2026-35471/): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in goshs (critical 9.8)
- [CVE-2026-40189](https://insights.sbomify.com/CVE-2026-40189/): goshs has a file-based ACL authorization bypass in goshs state-changing routes (critical 9.3)
- [CVE-2026-40903](https://insights.sbomify.com/CVE-2026-40903/): Goshs - ArtiPACKED Vulnerability – GitHub Actions Credential Persistence (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35392 and fix it if it is affected.

What it is: CVE-2026-35392 is a critical path traversal vulnerability in patrickhener goshs, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35392 exists.

Affected packages and fixed versions:
- github.com/patrickhener/goshs (Go): affected all versions; fixed in 1.1.5-0.20260401172448-237f3af891a9
- github.com/patrickhener/goshs (Go): affected all versions; fixed in 1.1.5-0.20260401172448-237f3af891a9
- github.com/patrickhener/goshs (Go): affected all versions; fixed in 1.1.5-0.20260401172448-237f3af891a9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35392/ (Markdown: https://insights.sbomify.com/CVE-2026-35392/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35392
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35392
- OSV: https://osv.dev/vulnerability/CVE-2026-35392

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35392/
Summaries are generated and may contain mistakes; the official description above is the record.