On Windows, git-sizer might run a git executable within the repository being analyzed

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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-sizer against a repository that might contain hostile code, or, if you must… Run git-sizer against a bare clone of the hostile repository, or, if that is not possible… Make sure that the hostile repository doesn't…

Published by the source

15 Feb 2022, 01:57 UTC

Last modified by the source

9 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-57q7-rxqq-7vgp

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

# Patch Next advisory brief: GHSA-57q7-rxqq-7vgp

Advisory: On Windows, `git-sizer` might run a `git` executable within the repository being analyzed
IDs: GHSA-57q7-rxqq-7vgp
Record: https://patchnext.com/advisories/ghsa-57q7-rxqq-7vgp (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/github/git-sizer 1.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/github/git-sizer: affected <= 1.3.0; fixed in 1.4.0

## Suggested inspection (read-only)
- Go github.com/github/git-sizer: 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/github/git-sizer.
- 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-57q7-rxqq-7vgp (GitHub-reviewed advisory GHSA-57q7-rxqq-7vgp lists affected ranges: Go github.com/github/git-sizer >=0 <=1.3.0)

Commands are suggestions: review each one before running it.