charmbracelet/soft-serve HTTP responses disclose the existence and names of private repositories
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/charmbracelet/soft-serve 0.12.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/charmbracelet/soft-serve
- Affected
- >= 0.5.0, < 0.12.3
- Fixed in
- 0.12.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-fgxm-5hvv-x4vh lists affected ranges: Go github.com/charmbracelet/soft-serve >=0.5.0 <0.12.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-fgxm-5hvv-x4vh lists affected ranges: Go github.com/charmbracelet/soft-serve >=0.5.0 <0.12.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary Soft Serve answers Go's `?go-get=1` requests by walking up the requested path until it finds a repository, then rendering that repository's name and clone URL into a `go-import` meta tag. The walk checked that each candidate repository existed, but never that the caller could read it. A request for a path inside a private repository, such as `GET /secret/anything?go-get=1`, therefore returned `200` naming `secret` and its clone URL, even though `GET /secret?go-get=1` correctly returned `404`. The same `?go-get=1` exception in the HTTP access middleware also let requests reach the LFS and dumb-HTTP routes with the repository existence check skipped, where two LFS handlers dereferenced the missing repository and panicked. The same disclosure appears without `?go-get=1`. The Git and LFS routes answered a repository the caller could not read differently depending on whether it existed: an anonymous clone of a private repository got `401` while a missing one got `404`, and a…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-fgxm-5hvv-x4vh
- Revision 1 · created ·
Published from ghsa record GHSA-fgxm-5hvv-x4vh
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-fgxm-5hvv-x4vh Advisory: charmbracelet/soft-serve HTTP responses disclose the existence and names of private repositories IDs: GHSA-fgxm-5hvv-x4vh Record: https://patchnext.com/advisories/ghsa-fgxm-5hvv-x4vh (revision 2, source checked 31 Oct 2026, 06:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/charmbracelet/soft-serve 0.12.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/charmbracelet/soft-serve: affected >= 0.5.0, < 0.12.3; fixed in 0.12.3 ## Suggested inspection (read-only) - Go github.com/charmbracelet/soft-serve: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/charmbracelet/soft-serve. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-fgxm-5hvv-x4vh (GitHub-reviewed advisory GHSA-fgxm-5hvv-x4vh lists affected ranges: Go github.com/charmbracelet/soft-serve >=0.5.0 <0.12.3) - Verified: https://osv.dev/vulnerability/GHSA-fgxm-5hvv-x4vh (OSV record GHSA-fgxm-5hvv-x4vh lists affected ranges: Go github.com/charmbracelet/soft-serve >=0.5.0 <0.12.3 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…