Git LFS can execute a Git binary from the current directory

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-2020-27955: 82.32% estimated exploitation activity in the next 30 days; percentile 99.66 (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 On Windows, if Git LFS operates on a malicious repository with a git.bat or git.exe file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems. This occurs because on Windows, Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator. Patches This version should be patched in v2.12.1, which will be released in coordination with this security advisory. Workarounds Other than avoiding untrusted repositories, there is no workaround. For more information If you have any questions or comments about this advisory: Start a discussion in the Git LFS discussion page. If you cannot open a discussion, please email the core team using their usernames at github.com.

Published by the source

11 Feb 2022, 23:39 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4g4p-42wc-9f3m

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

# Patch Next advisory brief: CVE-2020-27955

Advisory: Git LFS can execute a Git binary from the current directory
IDs: CVE-2020-27955, GHSA-4g4p-42wc-9f3m
Record: https://patchnext.com/advisories/cve-2020-27955 (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: 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/git-lfs/git-lfs 2.12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/git-lfs/git-lfs: affected < 2.12.1; fixed in 2.12.1

## Suggested inspection (read-only)
- Go github.com/git-lfs/git-lfs: 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/git-lfs/git-lfs.
- 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-4g4p-42wc-9f3m (GitHub-reviewed advisory GHSA-4g4p-42wc-9f3m lists affected ranges: Go github.com/git-lfs/git-lfs >=0 <2.12.1)

Commands are suggestions: review each one before running it.