CVE-2026-69261: github.com/git-lfs/git-lfs · Git LFS may leak HTTP headers after redirections
Affects github.com/git-lfs/git-lfsSource GCVE Database
Not known to be exploited · CVSS 7.6 High : upgrade to 3.8.1 soon.
Data as of 20 Nov 2026, 15:54 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 7.6 |
|---|
- Patch
- Available – fixed in 3.8.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade github.com/git-lfs/git-lfs/v3 to 3.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/git-lfs/git-lfs | Affected
| Fixed in– |
| Gogithub.com/git-lfs/git-lfs/v3 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in Git LFS version 3.8.1, which fixes the issue by preventing forwarding of Cookie and Authorization headers to different hosts after redirections. Users should upgrade to version 3.8.1. There is no single workaround; however, users and administrators should review their systems to avoid unnecessary HTTP redirections and ensure that HTTP headers other than Authorization do not contain privileged or confidential information.
Description
Git LFS versions from 0.5.0 up to 2.13.3 and from 3.0.0 up to 3.8.0 may incorrectly forward Cookie HTTP headers to unintended hosts after HTTP redirections. Authorization headers are not forwarded incorrectly. This issue is fixed in version 3.8.1, which prevents forwarding Cookie and Authorization headers to hosts different from the original request. Users should upgrade to 3.8.1 to mitigate this risk.
References
- github.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xr (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-69261 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/12c92e05b3433494d4b8695943e7e230744d77d9 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/256d371024e6d2cf19efe675d8b9ad089785d0a1 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/537203a1fa08fdde4c16288fb039174ff0e692bb (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/d65324a7d5104c7a5dcb8c4959933695c8bc10fa (opens in a new tab)
- github.com/git-lfs/git-lfs (opens in a new tab)
- github.com/git-lfs/git-lfs/releases/tag/v3.8.1 (opens in a new tab)