Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.6
CVE-2026-69260: Git LFS can run commands on remote server via SSH URL
CVE-2026-69260 · published today
Summary
Git LFS may let an attacker insert shell commands into an SSH URL, causing the remote server to execute those commands if it does not properly filter input. This affects all versions from 0.5.0 onward. Upgrade to version 3.8.1 or set the lfs.sshTransfer option to never to stop transfers over SSH, and ensure your SSH service sanitizes incoming commands.
What to do
- Update debian git-lfs to version 3.8.1-1.
- Update github.com git-lfs to version 3.8.1.
- Update git-lfs github.com/git-lfs/git-lfs/v3 to version 3.8.1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | git-lfs | git-lfs | >= 0.5.0, <= 2.13.3 |
| Debian:12 | debian | git-lfs | All versions |
| Debian:14 | debian | git-lfs |
< 3.8.1-1 Fix: upgrade to 3.8.1-1
|
| go | github.com | git-lfs | >= 0.5.0, <= 2.13.3 |
| go | github.com | git-lfs |
>= 3.0.0, < 3.8.1 Fix: upgrade to 3.8.1
|
| Go | git-lfs | github.com/git-lfs/git-lfs | >= 0.5.0, <= 2.13.3 |
| Go | git-lfs | github.com/git-lfs/git-lfs/v3 |
>= 3.0.0, < 3.8.1 Fix: upgrade to 3.8.1
|
Original advisory text
Git LFS may attempt arbitrary remote commands via crafted SSH URLs
### 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.
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.
References
- https://github.com/git-lfs/git-lfs/commit/091a95a796739bd0b8f59d8deeea79a4529595...
- https://github.com/git-lfs/git-lfs/commit/92d81117d465469a61dcb78546dd3d88806b25...
- https://github.com/git-lfs/git-lfs/commit/af5f4579ac1155734bb08f00ca92b9e89f8b51...
- https://github.com/git-lfs/git-lfs/commit/d90ed66f2d465f8b3ba5fd6e4ac3c711c9e0a2...
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-w3f2-pr6x-wwjc
- https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/69xxx/CVE-2026-69260... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-69260
- https://security-tracker.debian.org/tracker/CVE-2026-69260 Vendor Advisory
- https://github.com/advisories/GHSA-w3f2-pr6x-wwjc
- https://github.com/git-lfs/git-lfs Product
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker full control (estimated)
Type
CWE-78OS Command Injection
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen19 Nov 2026
Sources
CVE-2026-69260 · NVD
CVE-2026-69260 · MITRE
CVE-2026-69260 · OSV
GHSA-w3f2-pr6x-wwjc · GHSA
DEBIAN-CVE-2026-69260 · OSV
GHSA-w3f2-pr6x-wwjc · OSV
Track software like this
Free during beta