Arbitrary code execution due to an uncontrolled search path for the git binary

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2021-28955: 1.72% estimated exploitation activity in the next 30 days; percentile 77.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

25 May 2021, 18:44 UTC

Last modified by the source

19 May 2025, 16:36 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m898-h4pm-pqfr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-28955

Advisory: Arbitrary code execution due to an uncontrolled search path for the git binary
IDs: CVE-2021-28955, GHSA-m898-h4pm-pqfr
Record: https://patchnext.com/advisories/cve-2021-28955 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/MichaelMure/git-bug 0.7.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/MichaelMure/git-bug: affected < 0.7.2; fixed in 0.7.2

## Suggested inspection (read-only)
- Go github.com/MichaelMure/git-bug: 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/MichaelMure/git-bug.
- 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-m898-h4pm-pqfr (GitHub-reviewed advisory GHSA-m898-h4pm-pqfr lists affected ranges: Go github.com/MichaelMure/git-bug >=0 <0.7.2)

Commands are suggestions: review each one before running it.