Git LFS cookie leak via HTTP redirect handling
Affects Git LFS 0.5.0 through 3.8.0 when an HTTP redirect sends a request carrying a Cookie header to a different host, port, or scheme. Fixed in 3.8.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.8.1
- Who is exposed
- Specific setups only
Summary
Git LFS, a Git extension for versioning large files, can forward a Cookie header after an HTTP redirect to a host other than the one the cookie was meant for. An attacker controlling that host can reach the cookies it receives remotely, without logging in, though the victim must take an action such as following the redirect; this can expose credentials or other confidential values.
Written by a model
Original description
Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS may forward a Cookie header after an HTTP redirect to a host other than the one for which the header was intended. That unintended host can therefore receive cookies containing credentials or other confidential values. Authorization headers are never forwarded to inappropriate hosts and are not the affected secret in this vulnerability. This issue is fixed in version 3.8.1.
Who should check
Anyone running git-lfs from 0.5.0 through 3.8.0, including Go builds of github.com/git-lfs/git-lfs.
“This problem exists in all versions since 0.5.0”
What to do
Check whether your setup matches what the bug needs.
Git LFS receives an HTTP redirect to a different host, port, or scheme while a request carries a Cookie header Affects Git LFS versions from 0.5.0 through 3.8.0Upgrade to a fixed version: 3.8.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-69261 (Git LFS may leak HTTP headers after redirections), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-69261 (entry last updated 2026-11-19):
Affected:
- git-lfs git-lfs: from 0.5.0, through 2.13.3; from 3.0.0, fixed in 3.8.1
Fixed versions: 3.8.1.
Conditions (all must be true for the bug to be hit):
- Git LFS receives an HTTP redirect to a different host, port, or scheme while a request carries a Cookie header (source: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xr)
- Affects Git LFS versions from 0.5.0 through 3.8.0 (source: https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-69261 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69261 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xr
- https://github.com/git-lfs/git-lfs/commit/12c92e05b3433494d4b8695943e7e230744d77d9
- https://github.com/git-lfs/git-lfs/commit/256d371024e6d2cf19efe675d8b9ad089785d0a1
- https://github.com/git-lfs/git-lfs/commit/537203a1fa08fdde4c16288fb039174ff0e692bb
- https://github.com/git-lfs/git-lfs/commit/d65324a7d5104c7a5dcb8c4959933695c8bc10fa
- https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-69261
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69261"}.Affected versions
- git-lfs git-lfsFrom 0.5.0 · through 2.13.3; From 3.0.0 · fixed in 3.8.1
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 7.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · git-lfs/git-lfs · Advisory GHSA-x7xj-4j4f-88xr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-69261 |
| Record | NVD · CVE-2026-69261 |
| Other links 5 | |
| Repository | GitHub · git-lfs/git-lfs · Commit 12c92e05 |
| Repository | GitHub · git-lfs/git-lfs · Commit 256d3710 |
| Repository | GitHub · git-lfs/git-lfs · Commit 537203a1 |
| Repository | GitHub · git-lfs/git-lfs · Commit d65324a7 |
| Repository | GitHub · git-lfs/git-lfs · Release v3.8.1 |
Questions about CVE-2026-69261
Is CVE-2026-69261 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
After an HTTP redirect, Git LFS may forward certain headers to a host other than the one they were meant for. That other host can then receive Cookie header values, which may contain credentials or other confidential data.
Source: github.com
Which versions are affected by CVE-2026-69261?
git-lfs: from 0.5.0 through 2.13.3; from 3.0.0 before 3.8.1.
Source: cve.now feed data
Am I affected, and how do I check?
The listed range is Git LFS 0.5.0 through 2.13.3 and 3.0.0 through 3.8.0. The problem needs a redirect to a different host, port, or scheme while a request carries a Cookie header. To check a version, run git lfs version.
Source: github.com
How do I fix CVE-2026-69261?
Upgrade the 3.x line to Git LFS 3.8.1 or later. The facts list no fixed release for the 2.x line, which is affected through 2.13.3.
Source: github.com
Related
- CVE-2022-24826Git LFS can execute a binary from the current directory on Windows
- CVE-2026-105802Git LFS may execute arbitrary commands via crafted Git configurations
- CVE-2026-105803Git LFS may execute arbitrary commands via crafted Git LFS configurations
- CVE-2025-26625Git LFS may write to arbitrary files via crafted symlinks
- CVE-2024-53263Git LFS permits exfiltration of credentials via crafted HTTP URLs
- CVE-2026-69260Git LFS may attempt arbitrary remote commands via crafted SSH URLs
No corrections so far. Something wrong on this page? Report an error.