CVE-2026-69261: Git LFS may leak HTTP headers after redirections
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.
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
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.
Credited to SnailSploit.
References
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xr
- https://nvd.nist.gov/vuln/detail/CVE-2026-69261
- https://github.com/git-lfs/git-lfs/commit/12c92e05b3433494d4b8695943e7e230744d77d9
- https://github.com/git-lfs/git-lfs/commit/256d371024e6d2cf19efe675d8b9ad089785d0a1
- https://github.com/git-lfs/git-lfs/commit/537203a1fa08fdde4c16288fb039174ff0e692bb
- https://github.com/git-lfs/git-lfs/commit/d65324a7d5104c7a5dcb8c4959933695c8bc10fa
- https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
- https://github.com/advisories/GHSA-x7xj-4j4f-88xr
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 entriesCVE-2026-105802
Git LFS may execute arbitrary commands via crafted Git configurations
high8.6No fixNov 20, 2026CVE-2026-105803
Git LFS may execute arbitrary commands via crafted Git LFS configurations
high8.6No fixNov 20, 2026CVE-2026-69260
Git LFS may attempt arbitrary remote commands via crafted SSH URLs
high7.6No fixNov 20, 2026CVE-2025-26625
Git LFS may write to arbitrary files via crafted symlinks
high8.6Oct 17, 2025CVE-2024-53263
Git LFS permits exfiltration of credentials via crafted HTTP URLs
high8.5No fixJan 14, 2025
