CVE-2026-105802: Git LFS may execute arbitrary commands via crafted Git configurations

High

OSV id
GHSA-xrgv-7vx6-5vx6
Also known as
CVE-2026-105802
Published
Last modified

Affected packages

PackageAffected versionsFixed in
github.com/git-lfs/git-lfs
Go
>= 0.6.0, <= 2.13.3 after 2.13.3
github.com/git-lfs/git-lfs/v3
Go
>= 3.0.0, < 3.8.1 3.8.1

How to fix it

github.com/git-lfs/git-lfs (Go)

No fix yet. No fixed version of github.com/git-lfs/git-lfs has been released yet.

  • Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
  • Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
  • Pin away from the affected versions if an older release is not affected, or consider replacing the package.
  • Watch for the fix: a free AIssue account checks your lockfiles every day and emails you when a fixed version is released.

github.com/git-lfs/git-lfs/v3 (Go)

Upgrade github.com/git-lfs/git-lfs/v3 to 3.8.1 or later.

go get github.com/git-lfs/git-lfs/v3@v3.8.1
go mod tidy
  • Indirect Go modules are upgraded the same way (`go get module@version`).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

Impact

When fetching objects from a malicious repository, Git LFS may execute an arbitrary command or binary after incorrectly parsing the Git configuration options defined for a submodule.

Git LFS reads Git configuration options without checking for embedded line-ending control characters. By inserting control characters such as line feed (LF) into certain values, an attacker may be able to mimic options that cause Git LFS to execute an arbitrary command when fetching or adding objects.

Git LFS has resolved this issue by always using an unambiguous format to read and parse Git configuration options.

Patches

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

Workarounds

To work around the problem, users should prevent Git from initializing any submodules by disabling the fetch.recurseSubmodules and submodule.recurse configuration options and by never running the git submodule init command. Any submodules which have already been initialized in a repository may be deactivated with the git submodule deinit command.

For more information

If you have any questions or comments about this advisory:

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.