NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

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

highCVSS 4.0 7.6GHSA-w3f2-pr6x-wwjc

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.

Published Nov 20, 2026

Affected packages

github.com/git-lfs/git-lfs

Ecosystem
Go
Affected
>= 0.5.0, <= 2.13.3
Fixed in
No patched version yet
Check
go list -m github.com/git-lfs/git-lfs

github.com/git-lfs/git-lfs/v3

Ecosystem
Go
Affected
>= 3.0.0, < 3.8.1
Fixed in
3.8.1
Check
go list -m github.com/git-lfs/git-lfs/v3

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to dungNHVhust.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries