NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

CVE-2026-105803 — git-lfs

Fix: git-lfs/git-lfs@1ecddd4

CVE-2026-105803 is a CWE-777 vulnerability in github.com/git-lfs/git-lfs. A fix is available for github.com/git-lfs/git-lfs — see the affected versions and patch details below.

Git LFS may execute arbitrary commands via crafted Git LFS configurations

Also known asGHSA-x72p-hmqp-46hw
Published
Updated
Affected
2 pkgs
Patched
1 / 2
Exploits
None indexed
Exploitation data as of Nov 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected
🐹github.com/git-lfs/git-lfs🐹github.com/git-lfs/git-lfs/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/git-lfs/git-lfs≥ 1.3.0No fix
🐹Gogithub.com/git-lfs/git-lfs/v3≥ 3.0.0&&< 3.8.13.8.1go get github.com/git-lfs/git-lfs/v3@v3.8.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for CVE-2026-105803; check the affected-versions list above or the advisory for the patched release of github.com/git-lfs/git-lfs, then make sure no transitive dependency still pins the vulnerable range.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat Product Security rates this vulnerability as Important because successful exploitation can allow an attacker to execute arbitrary commands with the privileges of the local user. Although remote code execution is possible, it is not rated Critical because exploitation requires user interaction to clone or fetch…

Workaround published by Red Hat
Avoid interacting with untrusted repositories or remove the git-lfs package if large file storage support is not required. To remove the Git LFS package on Red Hat Enterprise Linux: # dnf remove git-lfs Caveats: Removing git-lfs disables tracking, downloading, and uploading large assets managed by Git LFS. If Git LFS is required in your environment, isolate Git operations on unverified repositories within an unprivileged container or sandbox with restricted filesystem and network access.
Source: Red Hat security advisory for CVE-2026-105803 (CC BY 4.0)

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is CVE-2026-105803 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2026-105803: git-lfs — Fixed in 3.8.1