cve.bz

CVE-2026-69260 Git LFS may attempt arbitrary remote commands via crafted SSH URLs

7.6 highEPSS 0.9%Fix available

High (7.6) in git-lfs git-lfs. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/git-lfs/git-lfs/v3 3.8.1.

On this page
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.

Severity

CVSS 4.0

7.6 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS
0.9% estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-69260 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69260?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69260?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-69260 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
git-lfs>= 0.5.0, <= 2.13.3
git-lfs>= 3.0.0, < 3.8.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w3f2-pr6x-wwjcGogithub.com/git-lfs/git-lfs>=0.5.0 <=2.13.3no fix published
GHSA-w3f2-pr6x-wwjcGogithub.com/git-lfs/git-lfs/v3>=3.0.0 <3.8.13.8.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13git-lfsno fix listedDEBIAN-CVE-2026-69260
Debian14git-lfs3.8.1-1DEBIAN-CVE-2026-69260
openSUSETumbleweedgit-lfs3.8.1-1.1openSUSE-SU-2026:12237-1

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because exploiting it allows remote arbitrary command execution with the privileges of the local user, though it requires user interaction to clone, fetch, or operate on a repository with a maliciously crafted SSH URL. In Red Hat environments, Git LFS operates as an optional client-side tool rather than an exposed network daemon, limiting the blast radius to the context of the executing user. Workflows that do not use Git LFS or that interact solely with verified remote endpoints are not exposed to this issue.

Red Hat's mitigation

Avoid cloning, fetching, or checking out untrusted Git repositories, submodules, or branches that contain unverified remote SSH URLs.

If Git Large File Storage functionality is not required on the system, remove the optional git-lfs package:

# dnf remove git-lfs

Caveats: Removing git-lfs will prevent managing, tracking, and downloading files stored via Git LFS. No system reboot or service restart is required.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgit-lfsAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-69260.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • googlesky/CVE-2026-69260 Harbor Check: matches CVE 0 stars, Python, created
    Git LFS <=3.8.0: ssh.GetLFSExeAndArgs interpolates the .lfsconfig SSH URL path unquoted into the remote command — shell metacharacters inje…

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON