CVE-2026-105803git-lfs vulnerability
CVE-2026-105803 is a vulnerability in git-lfs, rated high (8.6 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
The record does not classify the weakness yet; the description below says what the reporter found.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
A successful attack can read the data it protects and change data or behaviour.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade git-lfs to 3.8.1 or later.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- git-lfs. Start from where it runs and what it is connected to.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- People who open files and links. Mail, chat and browsers are the delivery path.
Questions to answer about your own systems
- Where does git-lfs run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Read more
Patches and commits
- github.com/git-lfs/git-lfs/commit/1ecddd431e63c551ae11c153df0e07f37d2b44ef
- github.com/git-lfs/git-lfs/commit/45c0c51c8a2d41a7d361b79f3d37f4fec46acc68
- github.com/git-lfs/git-lfs/commit/5182fdeccb834ed887746a557d0c736013704f39
- github.com/git-lfs/git-lfs/commit/62a727e7af1b0de0237c4d288ec0e977613df064
- github.com/git-lfs/git-lfs/commit/c5b3bff4e863022057557ad4be2ce5b5922b1a84
- github.com/git-lfs/git-lfs/commit/dcfb09ff56eec5825f3e95dbefbfdd520ec76d44
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.