# CVE-2026-34581: goshs has Auth Bypass via Share Token

> Attackers can bypass share token authentication in goshs to access restricted files and execute arbitrary code.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-jgfx-74g2-9r6g, GO-2026-5469

## What is CVE-2026-34581?

CVE-2026-34581 is a high-severity authentication bypass vulnerability in patrickhener goshs, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

goshs is a SimpleHTTPServer written in Go. From version 1.1.0 to before version 2.0.0-beta.2, when using the Share Token it is possible to bypass the limited selected file download with all the gosh functionalities, including code exec. This issue has been patched in version 2.0.0-beta.2.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

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 | From 1.1.0 | None |
| `github.com/patrickhener/goshs` | Go | From 1.1.0 | None |
| `github.com/patrickhener/goshs` | Go | From 1.1.0 | None |

Products: Goshs Goshs.

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

Upgrade to a fixed version.

## Is CVE-2026-34581 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34581 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-35392](https://insights.sbomify.com/CVE-2026-35392/): goshs has an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in goshs PUT Upload (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34581 is a high-severity authentication bypass vulnerability in patrickhener goshs, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34581 exists.

Affected packages and fixed versions:
- github.com/patrickhener/goshs (Go): affected from 1.1.0; no fix listed
- github.com/patrickhener/goshs (Go): affected from 1.1.0; no fix listed
- github.com/patrickhener/goshs (Go): affected from 1.1.0; no fix listed

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-34581/ (Markdown: https://insights.sbomify.com/CVE-2026-34581/index.md)
```

## Sources

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

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