# goshs: SSH host key verification disabled, allowing transparent MITM of every tunnelled HTTP request

Advisory record · `GHSA-mxg3-432p-mr72`

- **Identifiers:** `GHSA-mxg3-432p-mr72` · `GO-2026-5519`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html) · [CWE-322](https://cwe.mitre.org/data/definitions/322.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) · [CWE-322](https://agentprime.io/advisories/tag/cwe-322.md)
- **Published:** 15 May 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 May 2026, 17:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `goshs.de/goshs/v2` (Go): affected `<2.0.7`; fixed in `2.0.7`

## 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.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## 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-mxg3-432p-mr72)

## Sources

- [GitHub Advisory Database: GHSA-mxg3-432p-mr72](https://github.com/advisories/GHSA-mxg3-432p-mr72)
- [OSV: GHSA-mxg3-432p-mr72](https://osv.dev/vulnerability/GHSA-mxg3-432p-mr72)
- <https://github.com/patrickhener/goshs/security/advisories/GHSA-mxg3-432p-mr72>
- <https://github.com/patrickhener/goshs/commit/8f409cb08aacc6e94704334e8b1fb2cd50f5dd98>
- <https://github.com/patrickhener/goshs>
- <https://github.com/patrickhener/goshs/releases/tag/v2.0.7>

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-mxg3-432p-mr72>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mxg3-432p-mr72/>. Everything for agents: <https://agentprime.io/llms.txt>.