NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

CVE-2026-69260 — git-lfs

Fix: git-lfs/git-lfs@091a95a

CVE-2026-69260 is a OS Command Injection vulnerability in github.com/git-lfs/git-lfs. A fix is available for github.com/git-lfs/git-lfs — see the affected versions and patch details below.

Git LFS may attempt arbitrary remote commands via crafted SSH URLs

Also known asGHSA-w3f2-pr6x-wwjc
Published
Updated
Affected
2 pkgs
Patched
1 / 2
Exploits
None indexed
Exploitation data as of Nov 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected
🐹github.com/git-lfs/git-lfs🐹github.com/git-lfs/git-lfs/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

When Git LFS makes object transfer or authentication requests to a remote host via SSH, it passes the path component of the remote's SSH URL as part of a command to be executed, but does not properly format the URL's path component as a single argument. By inserting shell meta-characters into the SSH URL, an attacker may be able to execute arbitrary commands on the remote host, if the host passes the commands to a shell without sanitizing them first.

Git LFS has resolved this problem by fully quoting the arguments of the remote commands it sends via SSH.

As well, Git LFS has resolved a problem with the default HTTPS URLs used when an SSH URL is configured for a remote host and the host either does not support Git LFS remote commands sent via SSH or supports HTTP authentication via SSH for Git LFS but does not return an explicit HTTP URL in response to a git-lfs-authenticate remote command. In these cases, Git LFS now correctly encodes the HTTPS URL used to contact the remote host.

Patches

This problem exists in all versions since 0.5.0 and is patched in v3.8.1. All users should upgrade to v3.8.1.

Workarounds

Users may set the lfs.sshTransfer Git configuration option to never, after which Git LFS will not attempt any object transfers over SSH. However, Git LFS will still make authentication requests to SSH URLs, so administrators of Git LFS services should ensure their systems sanitize all commands received over SSH before executing them.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/git-lfs/git-lfs≥ 0.5.0No fix
🐹Gogithub.com/git-lfs/git-lfs/v3≥ 3.0.0&&< 3.8.13.8.1go get github.com/git-lfs/git-lfs/v3@v3.8.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for CVE-2026-69260; check the affected-versions list above or the advisory for the patched release of github.com/git-lfs/git-lfs, then make sure no transitive dependency still pins the vulnerable range.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

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…

Workaround published by Red Hat
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.
Source: Red Hat security advisory for CVE-2026-69260 (CC BY 4.0)

Frequently Asked Questions

### Impact When Git LFS makes object transfer or authentication requests to a remote host via SSH, it passes the path component of the remote's SSH URL as part of a command to be executed, but does not properly format the URL's path component as a single argument. By inserting shell meta-characters into the SSH URL, an attacker may be able to execute arbitrary commands on the remote host, if the host passes the commands to a shell without sanitizing them first. Git LFS has resolved this problem by fully quoting the arguments of the remote commands it sends via SSH. As well, Git LFS has res
O3 Security · Impact-Aware SCA

Is CVE-2026-69260 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2026-69260: git-lfs — Fixed in 3.8.1