New from Wiz Research: Critical NGINX flaw. Understand the risk and impact.

CVE-2026-69261: 
Git LFS vulnerability analysis and mitigation

Overview

CVE-2026-69261 is a credential-leaking vulnerability in Git LFS (Large File Storage) where, after receiving an HTTP redirection, Git LFS may forward Cookie headers to a different host than originally intended. This behavior can result in credentials or other secrets stored in HTTP cookies being sent to a malicious or unintended destination. The CVE was inserted into Feedly's threat intelligence feed on October 23, 2026, and its status is currently listed as "Reserved," indicating it is in early stages of public disclosure. No CVSS score has been publicly assigned at this time (Feedly).

Technical details

The root cause of this vulnerability is improper handling of HTTP redirects in Git LFS, specifically the failure to strip or scope Cookie headers when following redirects to a different host (CWE-601: URL Redirection to Untrusted Site / Open Redirect, or more precisely related to CWE-200: Exposure of Sensitive Information). When Git LFS follows an HTTP 3xx redirect, it does not validate whether the redirect target is the same host as the original request, and forwards authentication cookies to the new destination. This is analogous to the "cookie jar" mishandling seen in other HTTP client libraries. Exploitation requires that an attacker be able to influence the redirect destination, such as through a compromised or malicious server, a man-in-the-middle position, or a server-side redirect misconfiguration (Feedly, FreeBSD VuXML).

Impact

Successful exploitation could result in the leakage of HTTP cookies containing authentication tokens, session identifiers, or other sensitive credentials to an attacker-controlled host. This represents a confidentiality impact, potentially allowing an attacker to hijack authenticated sessions, access private repositories, or escalate privileges within systems that rely on cookie-based authentication with Git LFS. The integrity and availability of affected systems are not directly impacted, but credential theft could enable further lateral movement or unauthorized access (Feedly).

Exploitability

As of the available data, CVE-2026-69261 is listed as "Reserved" with no confirmed in-the-wild exploitation, no public proof-of-concept code, and no CISA KEV catalog entry. A reference to a GitHub account (SnailSploit) appeared in early Feedly tracking data, but no weaponized exploit or detailed PoC has been publicly confirmed. The EPSS score is not yet available. The vulnerability requires specific conditions — namely, an attacker's ability to control or influence HTTP redirect destinations — which somewhat limits opportunistic exploitation (Feedly).

Exploitation steps

  1. Reconnaissance: Identify targets using Git LFS to manage large files in repositories, particularly those authenticating via HTTP cookies to a Git hosting service.
  2. Set up malicious redirect: Position a server or compromise an intermediary that can issue HTTP 3xx redirect responses pointing to an attacker-controlled host.
  3. Trigger Git LFS operation: Cause the victim's Git LFS client to initiate an HTTP request (e.g., during a git lfs pull or git lfs push operation) that passes through the malicious redirect.
  4. Capture forwarded cookies: The Git LFS client, following the redirect without stripping Cookie headers, forwards authentication cookies to the attacker's server, where they are logged.
  5. Leverage stolen credentials: Use the captured session cookies to authenticate to the victim's Git hosting service, access private repositories, or perform actions on behalf of the victim (Feedly).

Indicators of compromise

  • Network: Unexpected outbound HTTP/HTTPS requests from Git LFS clients to unfamiliar or external hosts, especially following redirects from known Git LFS endpoints; HTTP requests containing Cookie: headers sent to hosts outside the expected domain.
  • Logs: Git LFS client logs showing HTTP 3xx redirect responses followed by requests to a different host than the original; server access logs showing authentication cookie values arriving from unexpected source IPs.
  • Process: Git LFS processes initiating connections to IP addresses or domains not associated with the configured LFS server.

Mitigation and workarounds

Users should update Git LFS to the latest patched version as soon as it is released by the maintainers. In the interim, consider disabling HTTP cookie-based authentication for Git LFS operations where possible, or restricting Git LFS traffic to trusted network paths. FreeBSD users can monitor the VuXML advisory and FreshPorts for updated packages (FreeBSD VuXML, FreshPorts). OpenSUSE users should apply updates referenced in the security announcement (openSUSE Security).

Community reactions

The vulnerability has been tracked by FreeBSD's VuXML database and FreshPorts, indicating it has received attention from the BSD security community. An openSUSE security announcement has also been issued, suggesting Linux distribution maintainers are actively packaging fixes. No notable researcher commentary or significant social media discussion has been identified at this time (FreeBSD VuXML, openSUSE Security).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

git-lfs

Affected

sid

git-lfs: 3.8.1-1

Fixed

trixie

git-lfs

Affected

RHEL / CentOS

Unknown

Alpine

Fixed

edge

git-lfs: 3.8.1-r0

Fixed

Source: This report was generated using AI

Related Git LFS vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-105803HIGH8.6
  • Git LFS logoGit LFS
  • git-lfs
NoYesNov 19, 2026
CVE-2026-105802HIGH8.6
  • Git LFS logoGit LFS
  • git-lfs
NoYesNov 19, 2026
CVE-2026-69261HIGH7.6
  • Git LFS logoGit LFS
  • git-lfs
NoYesNov 19, 2026
CVE-2026-69260HIGH7.6
  • Git LFS logoGit LFS
  • git-lfs
NoYesNov 19, 2026
CVE-2026-97054MEDIUM5.9
  • Go logoGo
  • fence-virtd
NoYesNov 11, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management