GHSA-w4xh-w33p-4v29
HIGHGHSA-w4xh-w33p-4v29 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in github.com/git-lfs/git-lfs. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-w4xh-w33p-4v29 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
GitHub Git LFS Arbitrary command execution vulnerability
Blast Radius
github.com/git-lfs/git-lfsReal-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
GitHub Git LFS before 2.1.1 allows remote attackers to execute arbitrary commands via an ssh URL with an initial dash character in the hostname, located on a url = line in a .lfsconfig file within a repository.
Specific Go Packages Affected
github.com/git-lfs/git-lfs/lfsapi
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/git-lfs/git-lfs | all versions | 2.1.1-0.20170519163204-f913f5f9c7c6 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/git-lfs/git-lfs to 2.1.1-0.20170519163204-f913f5f9c7c6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4xh-w33p-4v29 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w4xh-w33p-4v29 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w4xh-w33p-4v29. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w4xh-w33p-4v29 in your dependencies?
O3 detects GHSA-w4xh-w33p-4v29 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.