Git LFS can execute a binary from the current directory on Windows

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-2022-24826: 2.23% estimated exploitation activity in the next 30 days; percentile 82.75 (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 ..exe file as well as a file named git.exe, and git.exe is not found in PATH, the ..exe program will be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems. Similarly, if the malicious repository contains files named ..exe and cygpath.exe, and cygpath.exe is not found in PATH, the ..exe program will be executed when certain Git LFS commands are run. More generally, if the current working directory contains any file with a base name of . and a file extension from PATHEXT (except .bat and .cmd), and also contains another file with the same base name as a program Git LFS intends to execute (such as git, cygpath, or uname) and any file extension from PATHEXT (including .bat and .cmd), then, on Windows, when Git LFS attempts to execute the intended program the ..exe, ..com, etc., file will be executed instead, but only if the intended program is not found in any directory…

Published by the source

22 Apr 2022, 20:13 UTC

Last modified by the source

27 Jan 2023, 05:01 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6rw3-3whw-jvjj

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

# Patch Next advisory brief: CVE-2022-24826

Advisory: Git LFS can execute a binary from the current directory on Windows
IDs: CVE-2022-24826, GHSA-6rw3-3whw-jvjj
Record: https://patchnext.com/advisories/cve-2022-24826 (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: Partial vendor fix; fixed versions by package: github.com/git-lfs/git-lfs/v3 3.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/git-lfs/git-lfs: affected >= 2.12.1
- Go github.com/git-lfs/git-lfs/v3: affected >= 3.0.0, < 3.1.3; fixed in 3.1.3

## Suggested inspection (read-only)
- Go github.com/git-lfs/git-lfs: check the installed version with your package manager.
- Go github.com/git-lfs/git-lfs/v3: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/git-lfs/git-lfs, github.com/git-lfs/git-lfs/v3.
- 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-6rw3-3whw-jvjj (GitHub-reviewed advisory GHSA-6rw3-3whw-jvjj lists affected ranges: Go github.com/git-lfs/git-lfs/v3 >=3.0.0 =2.12.1)

Commands are suggestions: review each one before running it.