# soft-serve vulnerable to SSRF via unvalidated LFS endpoint in repo import

Advisory record · `GHSA-3fvx-xrxq-8jvv`

- **Identifiers:** `GHSA-3fvx-xrxq-8jvv` · `CVE-2026-30832` · `GO-2026-4634`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 6 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Mar 2026, 22:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

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

## Affected packages

- `github.com/charmbracelet/soft-serve` (Go): affected `>=0.6.0, <0.11.4`; fixed in `0.11.4`

## Machine-written summary

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

> Soft-serve versions from 0.6.0 before 0.11.4 are vulnerable to server-side request forgery through the LFS endpoint given to repo import (\`--lfs-endpoint\`) and to mirror syncs that reuse it. Any authenticated SSH user can make the server send HTTP requests to internal or private addresses, including cloud metadata services, and a user hosting a fake LFS server can read some internal responses. Upgrade to soft-serve 0.11.4, which contains the fix.

Written 7 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.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3fvx-xrxq-8jvv)

## Sources

- [GitHub Advisory Database: GHSA-3fvx-xrxq-8jvv](https://github.com/advisories/GHSA-3fvx-xrxq-8jvv)
- [OSV: GHSA-3fvx-xrxq-8jvv](https://osv.dev/vulnerability/GHSA-3fvx-xrxq-8jvv)
- <https://github.com/charmbracelet/soft-serve/security/advisories/GHSA-3fvx-xrxq-8jvv>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-30832>
- <https://github.com/charmbracelet/soft-serve/commit/3ef660098ab37a7950457da8ecc25b516e37ce4e>
- <https://github.com/charmbracelet/soft-serve>
- <https://github.com/charmbracelet/soft-serve/releases/tag/v0.11.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-3fvx-xrxq-8jvv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3fvx-xrxq-8jvv/>. Everything for agents: <https://agentprime.io/llms.txt>.