CVE-2026-69261 — git-lfs
Fix: git-lfs/git-lfs@12c92e0CVE-2026-69261 is a CWE-522 vulnerability in github.com/git-lfs/git-lfs. A fix is available for github.com/git-lfs/git-lfs — see the affected versions and patch details below.
Git LFS may leak HTTP headers after redirections
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/git-lfs/git-lfs🐹github.com/git-lfs/git-lfs/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/git-lfs/git-lfs | ≥ 0.5.0 | No fix |
| 🐹Go | github.com/git-lfs/git-lfs/v3 | ≥ 3.0.0&&< 3.8.1 | 3.8.1go get github.com/git-lfs/git-lfs/v3@v3.8.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2026-69261; check the affected-versions list above or the advisory for the patched release of github.com/git-lfs/git-lfs, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated as Moderate impact because exploitation requires a user to interact with an untrusted or compromised Git repository that issues an external redirect, preventing unprompted remote compromise. In Red Hat environments, Git LFS is invoked as a client-side helper during repository operations…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2026-69261 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-69261 in your dependencies?
Find it across Go, including transitive dependencies.