Skip to main content
Menu
CVEs

Git LFS command execution in .lfsconfig file handling

Affects git-lfs 1.3.0 through 2.13.3 and v3 3.0.0 through 3.8.0 when fetching objects from a malicious repository. CVSS rates it High (8.6).

CVE-2026-105803Published November 19, 2026, updated

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.1
Who is exposed
Specific setups only

Summary

Git LFS, an extension for versioning large files with Git, can be made to run attacker-chosen commands. A crafted .lfsconfig file in a repository can trigger this remotely, without logging in, though the victim must take an action such as fetching objects from the repository.

Written by a model

Original description

Git LFS is a Git extension for versioning large files. From 1.3.0 until 3.8.1, Git LFS does not correctly filter the limited set of options permitted in a repository's .lfsconfig file when option keys contain certain additional components. Crafted keys can mimic options that configure Git LFS to use a custom command to transfer objects, causing Git LFS to execute an attacker-selected command or binary while fetching objects. This issue is fixed in version 3.8.1.

Who should check

Teams running git-lfs 1.3.0-2.13.3 or v3 3.0.0-3.8.0 that clone or fetch from untrusted repositories. The v2 line has no patch.

“1.3.0-2.13.3”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects git-lfs 1.3.0 through 2.13.3 (github.com/git-lfs/git-lfs) and v3 3.0.0 through 3.8.0 (github.com/git-lfs/git-lfs/v3). The attack happens when Git LFS fetches objects from a malicious repository.
  2. Upgrade to a fixed version: 3.8.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-105803 (Git LFS may execute arbitrary commands via crafted Git LFS configurations), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-105803 (entry last updated 2026-11-19):
Affected:
- git-lfs git-lfs: from 1.3.0, through 2.13.3; from 3.0.0, fixed in 3.8.1
Fixed versions: 3.8.1.
Conditions (all must be true for the bug to be hit):
- Affects git-lfs 1.3.0 through 2.13.3 (github.com/git-lfs/git-lfs) and v3 3.0.0 through 3.8.0 (github.com/git-lfs/git-lfs/v3). (source: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x72p-hmqp-46hw)
- The attack happens when Git LFS fetches objects from a malicious repository. (source: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x72p-hmqp-46hw)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-105803 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-105803 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x72p-hmqp-46hw
- https://github.com/git-lfs/git-lfs/commit/1ecddd431e63c551ae11c153df0e07f37d2b44ef
- https://github.com/git-lfs/git-lfs/commit/45c0c51c8a2d41a7d361b79f3d37f4fec46acc68
- https://github.com/git-lfs/git-lfs/commit/5182fdeccb834ed887746a557d0c736013704f39
- https://github.com/git-lfs/git-lfs/commit/62a727e7af1b0de0237c4d288ec0e977613df064
- https://github.com/git-lfs/git-lfs/commit/c5b3bff4e863022057557ad4be2ce5b5922b1a84
- https://github.com/git-lfs/git-lfs/commit/dcfb09ff56eec5825f3e95dbefbfdd520ec76d44
- https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-105803
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-105803"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure15/25Specific setups only, CISA rates it automatable
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.6/10CVSS 8.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated

Evidence 10

Questions about CVE-2026-105803

Is CVE-2026-105803 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A crafted Git LFS configuration can make Git LFS run an arbitrary command or binary of the attacker's choice while it fetches objects from a malicious repository.

Source: github.com

Which versions are affected by CVE-2026-105803?

git-lfs: from 1.3.0 through 2.13.3; from 3.0.0 before 3.8.1.

Source: cve.now feed data

Am I affected, and how do I check?

The affected range is git-lfs 1.3.0 through 2.13.3 (github.com/git-lfs/git-lfs) and v3 3.0.0 through 3.8.0 (github.com/git-lfs/git-lfs/v3). To check a installed version, run `git lfs version`.

Source: github.com

How do I fix CVE-2026-105803?

The affected-range data lists 3.8.1 as the fixed version for the v3 line. No fixed version is listed for the 1.3.0 through 2.13.3 line.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.