HighGHSA-w3f2-pr6x-wwjcCVE-2026-69260

Git LFS may attempt arbitrary remote commands via crafted SSH URLs

Published 20 Nov 2026 · Updated 20 Nov 2026

Is your project on an affected github.com/git-lfs/git-lfs?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=0.5.0 <=2.13.3
Fixed in
No fix released
Affected
>=3.0.0 <3.8.1
Fixed in
3.8.1
Update to the fixed version for your release line, for example:go get github.com/git-lfs/git-lfs/v3@v3.8.1

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.

Is GHSA-w3f2-pr6x-wwjc in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/git-lfs/git-lfs, and gives you the command that fixes it.

More advisories for github.com/git-lfs/git-lfs

  • HighCVE-2026-105803Git LFS may execute arbitrary commands via crafted Git LFS configurations · 20 Nov 2026
  • HighCVE-2026-105802Git LFS may execute arbitrary commands via crafted Git configurations · 20 Nov 2026
  • HighCVE-2026-69261Git LFS may leak HTTP headers after redirections · 20 Nov 2026
  • LowCVE-2025-26625Git LFS may write to arbitrary files via crafted symlinks in github.com/git-lfs/git-lfs · 30 Oct 2025
  • HighCVE-2025-26625Git LFS may write to arbitrary files via crafted symlinks · 17 Oct 2025
  • LowCVE-2024-53263Git LFS permits exfiltration of credentials via crafted HTTP URLs in github.com/git-lfs/git-lfs · 15 Jan 2025
All 14 advisories for github.com/git-lfs/git-lfs

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.