Home/Research/Post

GHSA-x7xj-4j4f-88xr: Git LFS may leak HTTP headers after redirections

  • Severity: HIGH
  • CVE: CVE-2026-69261
  • Ecosystems: go, go
  • Packages: github.com/git-lfs/git-lfs, github.com/git-lfs/git-lfs/v3

### 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](https://github.com/git-lfs/git-lfs/discussions).
* For reports of additional vulnerabilities, please follow the Git LFS [security reporting policy](https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md).

Source: GitHub Security Advisories · 2026-11-20