GHSA-m898-h4pm-pqfr is a critical-severity (CVSS 9.8) CWE-427 vulnerability in github.com/MichaelMure/git-bug. O3 Security confirms whether GHSA-m898-h4pm-pqfr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Arbitrary code execution due to an uncontrolled search path for the git binary
Real-World Exposure
github.com/MichaelMure/git-bugReal-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
The go language recently addressed a security issue in the way that binaries are found before being executed. Some operating systems like Windows persist to have the current directory being part of the default search path, and having priority over the system-wide path.
This means that it's possible for a malicious user to craft for example a git.bat command, commit it and push it in a repository. Later when git-bug search for the git binary, this malicious executable can take priority and be executed.
Who is impacted
This issue happen on Windows and some other operating systems with a badly configured PATH.
All version prior to 0.7.2 are vulnerable to this issue.
Patches
Version 0.7.2 fix this issue. Users should update as soon as possible.
References
More details about this issue can be found here.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/MichaelMure/git-bug | all versions | 0.7.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/MichaelMure/git-bug. 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/MichaelMure/git-bug to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m898-h4pm-pqfr 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-m898-h4pm-pqfr 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-m898-h4pm-pqfr. 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-m898-h4pm-pqfr in your dependencies?
O3 detects GHSA-m898-h4pm-pqfr across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.