Skip to main content
Menu
CVEs

Git LFS remote command injection via crafted SSH URLs

Affects Git LFS 0.5.0 through 2.13.3 and 3.0.0 through 3.8.0 when object transfer or authentication requests go to a remote host over SSH URLs. Fixed in 3.8.1.

CVE-2026-69260EUVD-2026-130396Published November 19, 2026, updated

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

Summary

Git LFS, a Git extension for versioning large files, can be made to run arbitrary commands through crafted SSH URLs. An attacker on the network can trigger this remotely without logging in, but it requires a user to take an action and depends on the remote Git LFS service passing received commands to a shell without adequate sanitization.

Written by a model

Original description

Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS does not format the SSH URL path component as a single argument when constructing remote object-transfer or authentication commands. Shell metacharacters in the SSH URL can therefore escape the intended path argument and cause arbitrary command execution when the remote Git LFS service passes received commands to a shell without adequate sanitization. Git LFS also incorrectly encodes default HTTPS URLs when an SSH URL is configured and the remote host either does not support Git LFS remote commands over SSH or supports HTTP authentication over SSH but git-lfs-authenticate does not return an explicit HTTP URL. This issue is fixed in version 3.8.1.

Who should check

Teams running Git LFS 0.5.0 through 3.8.0 that use SSH URLs in lfs.url or lfs.pushurl, and admins of Git LFS services whose SSH hosts pass received commands to a shell.

Not fixed by: Setting lfs.sshTransfer to never still leaves SSH authentication requests active.

“This problem exists in all versions since 0.5.0 and is patched in v3.8.1.”

github.com

What to do

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

    Git LFS uses an SSH URL for object transfer or authentication requests to the remote host. Affects Git LFS versions from 0.5.0 up to 3.8.0; patched in 3.8.1. A separate HTTPS URL encoding problem applies when the remote host does not support Git LFS remote commands over SSH, or supports HTTP authentication over SSH but does not return an explicit HTTP URL.
  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-69260 (Git LFS may attempt arbitrary remote commands via crafted SSH URLs), 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-69260 (entry last updated 2026-11-19):
Affected:
- git-lfs git-lfs: from 0.5.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):
- Git LFS uses an SSH URL for object transfer or authentication requests to the remote host. (source: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-w3f2-pr6x-wwjc)
- Affects Git LFS versions from 0.5.0 up to 3.8.0; patched in 3.8.1. (source: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-w3f2-pr6x-wwjc)
- A separate HTTPS URL encoding problem applies when the remote host does not support Git LFS remote commands over SSH, or supports HTTP authentication over SSH but does not return an explicit HTTP URL. (source: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-w3f2-pr6x-wwjc)
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-69260 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69260 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-w3f2-pr6x-wwjc
- https://github.com/git-lfs/git-lfs/commit/091a95a796739bd0b8f59d8deeea79a452959508
- https://github.com/git-lfs/git-lfs/commit/92d81117d465469a61dcb78546dd3d88806b25fd
- https://github.com/git-lfs/git-lfs/commit/af5f4579ac1155734bb08f00ca92b9e89f8b51df
- https://github.com/git-lfs/git-lfs/commit/d90ed66f2d465f8b3ba5fd6e4ac3c711c9e0a2d6
- 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-69260
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-69260"}.

Affected versions

cve.now Index

21Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 7.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active

Timeline

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

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

  4. Record last updated

Evidence 8

Questions about CVE-2026-69260

Is CVE-2026-69260 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?

When Git LFS sends object transfer or authentication requests to a remote host over SSH, a crafted SSH URL can lead Git LFS to attempt running arbitrary commands on that host. This happens if the host passes the received commands to a shell without sanitizing them.

Source: github.com

Which versions are affected by CVE-2026-69260?

git-lfs: from 0.5.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?

Git LFS versions 0.5.0 through 2.13.3 and 3.0.0 through 3.8.0 are affected, and the problem exists in all versions since 0.5.0 until the 3.8.1 fix. The relevant setup is Git LFS using an SSH URL for object transfer or authentication with a remote host; running git lfs version shows the installed version.

Source: github.com

How do I fix CVE-2026-69260?

Upgrade Git LFS to version 3.8.1 or later, which contains the patch.

Source: github.com

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