CVE-2026-105802

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-130403 (ENISA EUVD) · GHSA-xrgv-7vx6-5vx6 (GitHub Security Advisories)Source: ENISA EUVD

8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Git LFS is a Git extension for versioning large files. From 0.6.0 until 3.8.1, Git LFS reads Git configuration options defined for a submodule without checking certain values for embedded line-ending control characters. A malicious repository can insert control characters such as line feed (LF) into those values to mimic options that cause Git LFS to execute an attacker-controlled command or binary while fetching or adding objects. This issue is fixed in version 3.8.1.

CVSS
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
39
EG Risk 39/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.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.
EPSS PROB
0.6%
EPSS %ILE
47th
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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 20, 2026

Advisory Details (4)

Auto-updated Nov 19, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v3.8.1

Patch available: git-lfs/git-lfs v3.8.1

https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
GitHub commit

commit 39b73aa4db82 (git-lfs/git-lfs)

Fix landed in git-lfs/git-lfs commit 39b73aa4db82 — awaiting tagged release

https://github.com/git-lfs/git-lfs/commit/39b73aa4db821fea6f0da8320128e5e1b919942d
GitHub commit

commit 1b2672aaa290 (git-lfs/git-lfs)

Fix landed in git-lfs/git-lfs commit 1b2672aaa290 — awaiting tagged release

https://github.com/git-lfs/git-lfs/commit/1b2672aaa29016e8004369df1406d2a73057f45f
GitHub advisoryMentions a patch (unverified)

Git LFS may execute arbitrary commands via crafted Git 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-xrgv-7vx6-5vx6

Vendor Advisories for CVE-2026-105802(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 / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/git-lfs/git-lfs—ghsa
gogithub.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.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/git-lfs/git-lfs—
  • 0.6.0 through 2.13.3: no fix on record
—
github.com/git-lfs/git-lfs/v3—
  • 3.0.0 up to 3.8.1: fixed in 3.8.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-11-20 22:28 UTCEchelonGraph re-scored
  3. 2026-11-20 22:28 UTCGHSA enrichmentGHSA-xrgv-7vx6-5vx6 · GitHub severity HIGH
  4. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-20 15:53 UTCGHSA enrichmentGHSA-xrgv-7vx6-5vx6 · GitHub severity HIGH
  6. 2026-11-19 18:03 UTCENISA EUVD ID recordedEUVD-2026-130403 · Source: ENISA EUVD
  7. 2026-11-19 17:28 UTCEchelonGraph re-scored
  8. 2026-11-19 16:59 UTCEchelonGraph re-scoredFirst assessed: 8.6 HIGH
  9. 2026-11-19 16:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-105802?
CVE-2026-105802 is a high-severity vulnerability; its CVE record was published on November 19, 2026. Git LFS is a Git extension for versioning large files. From 0.6.0 until 3.8.1, Git LFS reads Git configuration options defined for a submodule without checking certain values for embedded line-ending control characters. A malicious repository can insert control characters such as line feed (LF)…
When was the CVE record for CVE-2026-105802 published?
The CVE record for CVE-2026-105802 was published on November 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-105802 actively exploited?
CVE-2026-105802 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105802?
CVE-2026-105802 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105802?
A fix for CVE-2026-105802 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105802 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-105802

Explore →

Is Your Infrastructure Affected by CVE-2026-105802?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.