HighGHSA-x72p-hmqp-46hwCVE-2026-105803

Git LFS may execute arbitrary commands via crafted Git LFS configurations

Published 20 Nov 2026 · Updated 20 Nov 2026

Is your project on an affected github.com/git-lfs/git-lfs?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.3.0 <=2.13.3
Fixed in
No fix released
Affected
>=3.0.0 <3.8.1
Fixed in
3.8.1
Update to the fixed version for your release line, for example:go get github.com/git-lfs/git-lfs/v3@v3.8.1

Details

Impact

When fetching objects from a malicious repository, Git LFS may execute an arbitrary command or binary after failing to sufficiently restrict the set of configuration options defined in an .lfsconfig file in the repository.

Git LFS permits a limited set of configuration options to be defined in an .lfsconfig file at the root of a Git repository, but does not filter these options correctly if their keys contain certain additional components, which allows an attacker to mimic options that configure Git LFS to use a custom command to transfer objects. An attacker can then provide an arbitrary command which Git LFS will invoke when fetching objects.

Git LFS has resolved this issue by correctly restricting the configuration of custom object transfer commands to local Git configuration files.

Patches

This problem exists in all versions since 1.3.0 and is patched in v3.8.1. All users should upgrade to v3.8.1.

Workarounds

No single workaround exists other than to disable Git LFS entirely. As far as possible, users and administrators should avoid cloning repositories from untrusted sources.

For more information

If you have any questions or comments about this advisory:

Is GHSA-x72p-hmqp-46hw in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/git-lfs/git-lfs, and gives you the command that fixes it.

More advisories for github.com/git-lfs/git-lfs

  • HighCVE-2026-105802Git LFS may execute arbitrary commands via crafted Git configurations · 20 Nov 2026
  • HighCVE-2026-69261Git LFS may leak HTTP headers after redirections · 20 Nov 2026
  • HighCVE-2026-69260Git LFS may attempt arbitrary remote commands via crafted SSH URLs · 20 Nov 2026
  • LowCVE-2025-26625Git LFS may write to arbitrary files via crafted symlinks in github.com/git-lfs/git-lfs · 30 Oct 2025
  • HighCVE-2025-26625Git LFS may write to arbitrary files via crafted symlinks · 17 Oct 2025
  • LowCVE-2024-53263Git LFS permits exfiltration of credentials via crafted HTTP URLs in github.com/git-lfs/git-lfs · 15 Jan 2025
All 14 advisories for github.com/git-lfs/git-lfs

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.