CVSS 4.0
7.6 highCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NHigh (7.6) in git-lfs git-lfs. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/git-lfs/git-lfs/v3 3.8.1.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:Ngithub.com/git-lfs/git-lfs/v3 (Go): fixed in 3.8.1Explain CVE-2026-69260 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69260?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69260?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-69260 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| git-lfs | >= 0.5.0, <= 2.13.3 |
| git-lfs | >= 3.0.0, < 3.8.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-w3f2-pr6x-wwjc | Go | github.com/git-lfs/git-lfs | >=0.5.0 <=2.13.3 | no fix published |
| GHSA-w3f2-pr6x-wwjc | Go | github.com/git-lfs/git-lfs/v3 | >=3.0.0 <3.8.1 | 3.8.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | git-lfs | no fix listed | DEBIAN-CVE-2026-69260 |
| Debian | 14 | git-lfs | 3.8.1-1 | DEBIAN-CVE-2026-69260 |
| openSUSE | Tumbleweed | git-lfs | 3.8.1-1.1 | openSUSE-SU-2026:12237-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · openSUSE.
Red Hat rates this Important.
This vulnerability is rated as Important because exploiting it allows remote arbitrary command execution with the privileges of the local user, though it requires user interaction to clone, fetch, or operate on a repository with a maliciously crafted SSH URL. In Red Hat environments, Git LFS operates as an optional client-side tool rather than an exposed network daemon, limiting the blast radius to the context of the executing user. Workflows that do not use Git LFS or that interact solely with verified remote endpoints are not exposed to this issue.
Avoid cloning, fetching, or checking out untrusted Git repositories, submodules, or branches that contain unverified remote SSH URLs.
If Git Large File Storage functionality is not required on the system, remove the optional git-lfs package:
# dnf remove git-lfs
Caveats: Removing git-lfs will prevent managing, tracking, and downloading files stored via Git LFS. No system reboot or service restart is required.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | git-lfs | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-69260.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.