GHSA-57q7-rxqq-7vgp
On Windows, `git-sizer` might run a `git` executable within the repository being analyzed
Impact
On Windows, if git-sizer is run against a non-bare repository, and that repository has an executable called git.exe, git.bat, etc., then that executable might be run by git-sizer rather than the system git executable. An attacker could try to use social engineering to get a victim to run git-sizer against a hostile repository and thereby get the victim to run arbitrary code.
On Linux or other Unix-derived platforms, a similar problem could occur if the user's PATH has the current directory before the path to the standard git executable, but this is would be a very unusual configuration that has been known for decades to lead to all kinds of security problems.
Patches
Users should update to git-sizer v1.4.0
Workarounds
If you are on Windows, then either
- Don't run
git-sizeragainst a repository that might contain hostile code, or, if you must… - Run
git-sizeragainst a bare clone of the hostile repository, or, if that is not possible… - Make sure that the hostile repository doesn't have an executable in its top-level directory before running
git-sizer.
If you are on Linux or other Unix-based system, then (for myriad reasons!) don't add the current directory to your PATH.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in the
git-sizerproject. - Email us at GitHub support.
What each source reports
GitHub AdvisoriesNo score
On Windows, `git-sizer` might run a `git` executable within the repository being analyzed
Impact
On Windows, if git-sizer is run against a non-bare repository, and that repository has an executable called git.exe, git.bat, etc., then that executable might be run by git-sizer rather than the system git executable. An attacker could try to use social engineering to get a victim to run git-sizer against a hostile repository and thereby get the victim to run arbitrary code.
On Linux or other Unix-derived platforms, a similar problem could occur if the user's PATH has the current directory before the path to the standard git executable, but this is would be a very unusual configuration that has been known for decades to lead to all kinds of security problems.
Patches
Users should update to git-sizer v1.4.0
Workarounds
If you are on Windows, then either
- Don't run
git-sizeragainst a repository that might contain hostile code, or, if you must… - Run
git-sizeragainst a bare clone of the hostile repository, or, if that is not possible… - Make sure that the hostile repository doesn't have an executable in its top-level directory before running
git-sizer.
If you are on Linux or other Unix-based system, then (for myriad reasons!) don't add the current directory to your PATH.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in the
git-sizerproject. - Email us at GitHub support.
- Record
GHSA-57q7-rxqq-7vgp- Updated
- 2026-11-02
OSVNo score
On Windows, `git-sizer` might run a `git` executable within the repository being analyzed
Impact
On Windows, if git-sizer is run against a non-bare repository, and that repository has an executable called git.exe, git.bat, etc., then that executable might be run by git-sizer rather than the system git executable. An attacker could try to use social engineering to get a victim to run git-sizer against a hostile repository and thereby get the victim to run arbitrary code.
On Linux or other Unix-derived platforms, a similar problem could occur if the user's PATH has the current directory before the path to the standard git executable, but this is would be a very unusual configuration that has been known for decades to lead to all kinds of security problems.
Patches
Users should update to git-sizer v1.4.0
Workarounds
If you are on Windows, then either
- Don't run
git-sizeragainst a repository that might contain hostile code, or, if you must… - Run
git-sizeragainst a bare clone of the hostile repository, or, if that is not possible… - Make sure that the hostile repository doesn't have an executable in its top-level directory before running
git-sizer.
If you are on Linux or other Unix-based system, then (for myriad reasons!) don't add the current directory to your PATH.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in the
git-sizerproject. - Email us at GitHub support.
- Record
GHSA-57q7-rxqq-7vgp- Updated
- 2026-11-02
OSVGO-2022-0424No score
On Windows, `git-sizer` might run a `git` executable within the repository being analyzed in github.com/github/git-sizer
On Windows, git-sizer might run a git executable within the repository being analyzed in github.com/github/git-sizer
- Record
GO-2022-0424- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/github/git-sizerGo | through 1.3.0 | 1.4.0 |
github.com/github/git-sizerGo | before 1.4.0 | 1.4.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-57q7-rxqq-7vgp is a vulnerability with no CVSS score yet in github.com/github/git-sizer, published February 15, 2022. No source lists public exploit code. Fixed in github.com/github/git-sizer 1.4.0.