Skip to content

ApplicationsHigh 8.6Patch available

CVE-2026-105803

Git LFS .lfsconfig parsing allows remote command execution

How scary is it?

updated 21 Nov 2026
  • Yes

    Works without logging in1

    No account needed, but a person has to act, such as opening a link or a file (CVSS PR:N, UI:P).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 8.6.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run git-lfs in an affected version>= 1.3.0 and <= 2.13.3 / >= 3.0.0 and < 3.8.1

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. A person takes an action, such as opening a link or a file

    CVSS user interaction: required (UI:P). A victim must click, open or otherwise cooperate.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. Recommendation, AI-writtenUpgrade Git LFS to 3.8.1 and audit .lfsconfig files and CI/build agents.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

CVSS
8.6Highscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.64%chance of exploitation in the next 30 daystop 49% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
19 Nov 2026analysed here 21 Nov 2026

Summary

Impact

Remote command execution during 'git lfs fetch' via crafted .lfsconfig keys, enabling attacker-chosen command/binary execution on the client or CI runner.

Triage

Exploitable
At runtime
Attack vector
network
Weaknesses
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
git-lfs>= 1.3.0 and <= 2.13.3>= 3.0.0 and < 3.8.1Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Git LFS 1.3.0–3.8.0
  • Repositories or CI/build agents that fetch attacker-controlled .lfsconfig

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability involves parsing of .lfsconfig files fetched by Git LFS or CI/build agents, which is not delivered via HTTP requests but through Git protocol or repository fetch mechanisms. Therefore, a web application firewall cannot filter or block the malicious input.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 19 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 19 Nov 2026Published
  2. 19 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 19 Nov 2026CVE record last updatedsame day later
  4. 20 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
  5. 21 Nov 2026Analysed by vulneraibility.com1 day later

Common questions

Is CVE-2026-105803 being exploited?

Not confirmed. CVE-2026-105803 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.

How severe is CVE-2026-105803?

CVE-2026-105803 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-105803?

Yes. A fix has been recorded for CVE-2026-105803. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-105803 affect?

CVE-2026-105803 affects Git LFS 1.3.0–3.8.0, Repositories or CI/build agents that fetch attacker-controlled .lfsconfig. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-105803?

Upgrade Git LFS to 3.8.1 and audit .lfsconfig files and CI/build agents.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

8 references in the CVE record, grouped by the tags the record gives them.

Other links (8)

  • github.com /git-lfs/git-lfs/security/advisories/GHSA-x72p-hmqp-46hw
  • 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
Show 2 more
  • github.com /git-lfs/git-lfs/commit/dcfb09ff56eec5825f3e95dbefbfdd520ec76d44
  • github.com /git-lfs/git-lfs/releases/tag/v3.8.1

Also tracked as GHSA-x72p-hmqp-46hw (OSV).

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.