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

Advisory record · `GHSA-rmxw-pq4x-3fvh`

- **Identifiers:** `GHSA-rmxw-pq4x-3fvh` · `CVE-2026-54719` · `GO-2026-6133`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 28 Jul 2026
- **Updated:** 18 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Jul 2026, 21:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/patrickhener/goshs` (Go): affected `<=1.1.4`; no fixed version yet
- `github.com/patrickhener/goshs/v2` (Go): affected `<2.1.1`; fixed in `2.1.1`
- `goshs.de/goshs` (Go): affected `<=1.1.4`; no fixed version yet
- `goshs.de/goshs/v2` (Go): affected `<2.1.1`; fixed in `2.1.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> goshs v2 versions before 2.1.1 are affected, and goshs 1.1.4 and earlier have no fixed version listed. An unauthenticated network attacker can use the ?bulk zip-download route to read files protected only by a per-folder .goshs access control. Upgrade to 2.1.1; no fix is listed for the v1 packages.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:50 UTC: First seen by agentprime
- 31 Oct 2026, 14:50 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rmxw-pq4x-3fvh)

## Sources

- [GitHub Advisory Database: GHSA-rmxw-pq4x-3fvh](https://github.com/advisories/GHSA-rmxw-pq4x-3fvh)
- [OSV: GHSA-rmxw-pq4x-3fvh](https://osv.dev/vulnerability/GHSA-rmxw-pq4x-3fvh)
- <https://github.com/goshs-labs/goshs/security/advisories/GHSA-rmxw-pq4x-3fvh>
- <https://github.com/goshs-labs/goshs/commit/7cf911a26ace737e1a55b7dc073e307a25f7fd1d>
- <https://github.com/goshs-labs/goshs>
- <https://github.com/goshs-labs/goshs/releases/tag/v2.1.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-rmxw-pq4x-3fvh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rmxw-pq4x-3fvh/>. Everything for agents: <https://agentprime.io/llms.txt>.
