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

High

OSV id
GHSA-x7xj-4j4f-88xr
Also known as
CVE-2026-69261
Published
Last modified

Affected packages

PackageAffected versionsFixed in
github.com/git-lfs/git-lfs
Go
>= 0.5.0, <= 2.13.3 after 2.13.3
github.com/git-lfs/git-lfs/v3
Go
>= 3.0.0, < 3.8.1 3.8.1

How to fix it

github.com/git-lfs/git-lfs (Go)

No fix yet. No fixed version of github.com/git-lfs/git-lfs has been released yet.

  • Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
  • Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
  • Pin away from the affected versions if an older release is not affected, or consider replacing the package.
  • Watch for the fix: a free AIssue account checks your lockfiles every day and emails you when a fixed version is released.

github.com/git-lfs/git-lfs/v3 (Go)

Upgrade github.com/git-lfs/git-lfs/v3 to 3.8.1 or later.

go get github.com/git-lfs/git-lfs/v3@v3.8.1
go mod tidy
  • Indirect Go modules are upgraded the same way (`go get module@version`).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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:

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.