soft-serve vulnerable to arbitrary code execution by crafting git-lfs requestsGHSA-m445-w3xr-vp2f
HIGHFix: charmbracelet/soft-serve@4daebddGHSA-m445-w3xr-vp2f is a high-severity (CVSS 8.1) OS Command Injection vulnerability in github.com/charmbracelet/soft-serve. A fix is available for github.com/charmbracelet/soft-serve — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-m445-w3xr-vp2f.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/charmbracelet/soft-serveReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Any servers using soft-serve server and git
Patches
0.7.5
Workarounds
None.
References
n/a.
It is possible for a user who can commit files to a repository hosted by Soft Serve to execute arbitrary code via environment manipulation and Git.
The issue is that Soft Serve passes all environment variables given by the client to git subprocesses. This includes environment variables that control program execution, such as LD_PRELOAD.
This can be exploited to execute arbitrary code by, for example, uploading a malicious shared object file to Soft Serve via Git LFS (uploading it via LFS ensures that it is not compressed on disk and easier to work with). The file will be stored under its SHA256 hash, so it has a predictable name.
This file can then be referenced in LD_PRELOAD via a Soft Serve SSH session that causes git to be invoked. For example:
LD_PRELOAD=/.../data/lfs/1/objects/a2/b5/a2b585befededf5f95363d06d83655229e393b1b45f76d9f989a336668665a2f ssh server git-upload-pack repo
The example LFS file patches a shared library function called by git to execute a shell.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/charmbracelet/soft-serve | all versions | 0.7.5go get github.com/charmbracelet/soft-serve@v0.7.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/charmbracelet/soft-serve, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/charmbracelet/soft-serve to 0.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m445-w3xr-vp2f is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-m445-w3xr-vp2f in your dependencies?
Find it across Go, including transitive dependencies.