# goshs has a file-based ACL authorization bypass in goshs state-changing routes

Advisory record · `GHSA-wvhv-qcqf-f3cx`

- **Identifiers:** `GHSA-wvhv-qcqf-f3cx` · `CVE-2026-40189` · `GO-2026-5728`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 10 Apr 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Apr 2026, 20:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

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

## Machine-written summary

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

> GHSA-wvhv-qcqf-f3cx: goshs, versions up to and including 1.1.4, does not apply its per-folder .goshs ACL and basic-auth checks to state-changing routes. An unauthenticated remote attacker can upload or overwrite files, create directories, and delete files in a protected folder, including the .goshs file itself, which then exposes previously protected content. No fixed version is listed; the source offers no workaround beyond applying the fix in its remediation guidance.

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

- 9.3 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 15:06 UTC: First seen by agentprime
- 31 Oct 2026, 15:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wvhv-qcqf-f3cx)

## Sources

- [GitHub Advisory Database: GHSA-wvhv-qcqf-f3cx](https://github.com/advisories/GHSA-wvhv-qcqf-f3cx)
- [OSV: GHSA-wvhv-qcqf-f3cx](https://osv.dev/vulnerability/GHSA-wvhv-qcqf-f3cx)
- <https://github.com/patrickhener/goshs/security/advisories/GHSA-wvhv-qcqf-f3cx>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40189>
- <https://github.com/patrickhener/goshs/commit/f212c4f4a126556bab008f79758e21a839ef2c0f>
- <https://github.com/patrickhener/goshs>
- <https://github.com/patrickhener/goshs/releases/tag/v2.0.0-beta.4>

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-wvhv-qcqf-f3cx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wvhv-qcqf-f3cx/>. Everything for agents: <https://agentprime.io/llms.txt>.
