NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-69261: Git LFS may leak HTTP headers after redirections

highCVSS 4.0 7.6GHSA-x7xj-4j4f-88xr

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:

Credited to SnailSploit.

References

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 entries