Git LFS may leak HTTP headers after redirections
Published 20 Nov 2026 · Updated 20 Nov 2026
Is your project on an affected github.com/git-lfs/git-lfs?
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
go get github.com/git-lfs/git-lfs/v3@v3.8.1Details
Impact
After receiving an HTTP redirection, Git LFS may forward certain HTTP headers to a host other than the one for which they were intended. While Authorization headers are never forwarded to inappropriate hosts, Cookie headers may be forwarded incorrectly.
Git LFS has resolved this issue by never forwarding Cookie headers to hosts other than the ones for which they were intended. In particular, after an HTTP redirection is received to a URL with a different scheme, host, or port than found in the URL of the current request, any Authorization and Cookie headers from the current request will not be sent in the redirected request.
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
No single workaround exists. As far as possible, users and administrators should review their systems to confirm no unnecessary HTTP redirections are performed, and that HTTP headers other than Authorization do not contain privileged or confidential information.
For more information
If you have any questions or comments about this advisory:
- For general questions, start a discussion in the Git LFS discussion forum.
- For reports of additional vulnerabilities, please follow the Git LFS security reporting policy.
Is GHSA-x7xj-4j4f-88xr 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-69260Git LFS may attempt arbitrary remote commands via crafted SSH URLs · 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
References
- Linkgithub.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xr
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-69261
- Linkgithub.com/git-lfs/git-lfs/commit/12c92e05b3433494d4b8695943e7e230744d77d9
- Linkgithub.com/git-lfs/git-lfs/commit/256d371024e6d2cf19efe675d8b9ad089785d0a1
- Linkgithub.com/git-lfs/git-lfs/commit/537203a1fa08fdde4c16288fb039174ff0e692bb
- Linkgithub.com/git-lfs/git-lfs/commit/d65324a7d5104c7a5dcb8c4959933695c8bc10fa
- Packagegithub.com/git-lfs/git-lfs
- Linkgithub.com/git-lfs/git-lfs/releases/tag/v3.8.1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.