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.
CVE-2026-105803
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-130399 (ENISA EUVD) · GHSA-x72p-hmqp-46hw (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS
- 8.6
- EG Score
- 8.6HIGHlow confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity86% × 45%Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 51st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 19, 2026
Last Modified
November 19, 2026
Advisory Details (8)
Auto-updated Nov 19, 2026v3.8.1
Patch available: git-lfs/git-lfs v3.8.1
https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1commit dcfb09ff56ee (git-lfs/git-lfs)
Fix landed in git-lfs/git-lfs commit dcfb09ff56ee — awaiting tagged release
https://github.com/git-lfs/git-lfs/commit/dcfb09ff56eec5825f3e95dbefbfdd520ec76d44commit c5b3bff4e863 (git-lfs/git-lfs)
Fix landed in git-lfs/git-lfs commit c5b3bff4e863 — awaiting tagged release
https://github.com/git-lfs/git-lfs/commit/c5b3bff4e863022057557ad4be2ce5b5922b1a84commit 62a727e7af1b (git-lfs/git-lfs)
Fix landed in git-lfs/git-lfs commit 62a727e7af1b — awaiting tagged release
https://github.com/git-lfs/git-lfs/commit/62a727e7af1b0de0237c4d288ec0e977613df064commit 5182fdeccb83 (git-lfs/git-lfs)
Fix landed in git-lfs/git-lfs commit 5182fdeccb83 — awaiting tagged release
https://github.com/git-lfs/git-lfs/commit/5182fdeccb834ed887746a557d0c736013704f39commit 45c0c51c8a2d (git-lfs/git-lfs)
Fix landed in git-lfs/git-lfs commit 45c0c51c8a2d — awaiting tagged release
https://github.com/git-lfs/git-lfs/commit/45c0c51c8a2d41a7d361b79f3d37f4fec46acc68commit 1ecddd431e63 (git-lfs/git-lfs)
Fix landed in git-lfs/git-lfs commit 1ecddd431e63 — awaiting tagged release
https://github.com/git-lfs/git-lfs/commit/1ecddd431e63c551ae11c153df0e07f37d2b44efGit LFS may execute arbitrary commands via crafted Git LFS configurations · Advisory · git-lfs/git-lfs · GitHub
Affected: v3.8.1. All users should upgrade to v3.8.1.
https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x72p-hmqp-46hwVendor Advisories for CVE-2026-105803(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/git-lfs/git-lfs | — | ghsa |
| go | github.com/git-lfs/git-lfs/v3 @ 3.8.1 (fixes >= 3.0.0, < 3.8.1) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.6% · 51st percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 46th percentile
- 2026-11-20 15:53 UTCGHSA enrichmentGHSA-x72p-hmqp-46hw · GitHub severity HIGH
- 2026-11-19 21:28 UTCEchelonGraph re-scored
- 2026-11-19 20:48 UTCEchelonGraph re-scored
- 2026-11-19 18:03 UTCENISA EUVD ID recordedEUVD-2026-130399 · Source: ENISA EUVD
- 2026-11-19 17:29 UTCEchelonGraph re-scored
- 2026-11-19 16:59 UTCEchelonGraph re-scoredFirst assessed: 8.6 HIGH
- 2026-11-19 16:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-105803?
When was the CVE record for CVE-2026-105803 published?
Is CVE-2026-105803 actively exploited?
What is the CVSS score of CVE-2026-105803?
How do I remediate CVE-2026-105803?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-105803
Is Your Infrastructure Affected by CVE-2026-105803?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.