CVE-2026-69260: Git LFS may attempt arbitrary remote commands via crafted SSH URLs
High
- OSV id
- GHSA-w3f2-pr6x-wwjc
- Also known as
- CVE-2026-69260
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| github.com/git-lfs/git-lfs Go |
>= 0.5.0, <= 2.13.3 | after 2.13.3 |
| github.com/git-lfs/git-lfs/v3 Go |
>= 3.0.0, < 3.8.1 | 3.8.1 |
How to fix it
github.com/git-lfs/git-lfs (Go)
No fix yet. No fixed version of github.com/git-lfs/git-lfs has been released yet.
- Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
- Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
- Pin away from the affected versions if an older release is not affected, or consider replacing the package.
- Watch for the fix: a free AIssue account checks your lockfiles every day and emails you when a fixed version is released.
github.com/git-lfs/git-lfs/v3 (Go)
Upgrade github.com/git-lfs/git-lfs/v3 to 3.8.1 or later.
go get github.com/git-lfs/git-lfs/v3@v3.8.1
go mod tidy
- Indirect Go modules are upgraded the same way (`go get module@version`).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
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.
References
- GHSA-w3f2-pr6x-wwjc on OSV.dev
- Web: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-w3f2-pr6x-wwjc
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-69260
- Web: https://github.com/git-lfs/git-lfs/commit/091a95a796739bd0b8f59d8deeea79a452959508
- Web: https://github.com/git-lfs/git-lfs/commit/92d81117d465469a61dcb78546dd3d88806b25fd
- Web: https://github.com/git-lfs/git-lfs/commit/af5f4579ac1155734bb08f00ca92b9e89f8b51df
- Web: https://github.com/git-lfs/git-lfs/commit/d90ed66f2d465f8b3ba5fd6e4ac3c711c9e0a2d6
- Package: https://github.com/git-lfs/git-lfs
- Web: https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.