# CVE-2026-54719: goshs: File-based .goshs ACL authorization bypass via the ?bulk zip-download route (unauthenticated read; residual of GHSA-wvhv-qcqf-f3cx)

> Unauthenticated attackers can bypass file access controls via the bulk download route to read protected files in goshs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-rmxw-pq4x-3fvh, GO-2026-6133

## What is CVE-2026-54719?

CVE-2026-54719 is a high-severity missing authorization vulnerability in goshs-labs goshs, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.1, the httpserver/updown.go bulkDownload handler for ?bulk&file= ZIP downloads did not call findEffectiveACL or applyCustomAuth, allowing unauthenticated reads of files protected only by .goshs folder ACLs and block lists. This issue is fixed in version 2.1.1. This vulnerability exists due to an incomplete fix for CVE-2026-40189.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

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

11 open source packages ship an affected version, including github.com/patrickhener/goshs, github.com/patrickhener/goshs/v2 and goshs.de/goshs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/patrickhener/goshs` | Go | All versions | None |
| `github.com/patrickhener/goshs` | Go | All versions to 1.1.4 | None |
| `github.com/patrickhener/goshs` | Go | All versions to 1.1.4 | None |
| `github.com/patrickhener/goshs/v2` | Go | All versions | 2.1.1 |
| `github.com/patrickhener/goshs/v2` | Go | All versions | 2.1.1 |
| `goshs.de/goshs` | Go | All versions | None |
| `goshs.de/goshs` | Go | All versions to 1.1.4 | None |
| `goshs.de/goshs` | Go | All versions to 1.1.4 | None |
| `goshs.de/goshs/v2` | Go | All versions | 2.1.1 |
| `goshs.de/goshs/v2` | Go | All versions | 2.1.1 |
| `goshs.de/goshs/v2` | Go | All versions | 2.1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-54719 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54719 is a high-severity missing authorization vulnerability in goshs-labs goshs, published on 28 Jul 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-54719 exists.

Affected packages and fixed versions:
- github.com/patrickhener/goshs (Go): affected all versions; no fix listed
- github.com/patrickhener/goshs (Go): affected all versions up to 1.1.4; no fix listed
- github.com/patrickhener/goshs (Go): affected all versions up to 1.1.4; no fix listed
- github.com/patrickhener/goshs/v2 (Go): affected all versions; fixed in 2.1.1
- github.com/patrickhener/goshs/v2 (Go): affected all versions; fixed in 2.1.1
- goshs.de/goshs (Go): affected all versions; no fix listed
- goshs.de/goshs (Go): affected all versions up to 1.1.4; no fix listed
- goshs.de/goshs (Go): affected all versions up to 1.1.4; no fix listed
- goshs.de/goshs/v2 (Go): affected all versions; fixed in 2.1.1
- goshs.de/goshs/v2 (Go): affected all versions; fixed in 2.1.1
- goshs.de/goshs/v2 (Go): affected all versions; fixed in 2.1.1

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

## Sources

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

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