Vulnerability · CVE-2025-26625

Git LFS is a Git extension for versioning large files.

Q: Which versions are affected?

Compare what you have installed with git-lfs git-lfs 0.5.2, < 3.7.1 0.5.2, < 3.7.1. Compare the installed version with the linked vendor advisory before you change production.

Q: What should an analyst verify?

CWE-59: Link Following. EPSS 1.05%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Published Oct 17, 2025 · catalog updated Oct 22, 2026 · Git LFS is a

Last checked Oct 26, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-26625. EPSS is 1.05%. Act only if a listed version of Git LFS is a is installed.

Gaps on this record

The stored product name is a package slug. The name on this page is taken from the title (Git LFS is a).
No vendor fix or required action is stored. Compare the linked advisory before you change production.

Severity: High8.6
Known exploitation: Not in CISA/VulnCheck KEV
EPSS: 1.05%
Remediation: Version ranges on file
Affected products: Bitnami git-lfs · vendor git-lfs git-lfs 0.5.2, < 3.7.1

Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

Bitnami git-lfs0.5.2 → 3.7.1
vendor git-lfs git-lfs 0.5.2, < 3.7.10.5.2, < 3.7.1

How to fix CVE-2025-26625

Upgrade
CVE-2025-26625 lists a fix boundary at 3.7.1. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.7.1
Advisory
Open the cve_org record and follow its fix.
Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-26625. EPSS is 1.05%. Act only if a listed version of Git LFS is a is installed.

Which versions are affected?

Compare what you have installed with git-lfs git-lfs 0.5.2, < 3.7.1 0.5.2, < 3.7.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-59: Link Following. EPSS 1.05%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Repository · github.com

Timeline

Detection, updates, and resolution for this record.

Oct 17, 2025 · NIST NVD
Detected
Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull c
Oct 21, 2026 · NIST NVD
Updated
Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull c
Oct 22, 2026 · GitHub Advisory Database
Fix available
git-lfs fixed in 3.7.1
Oct 22, 2026 · GitHub Advisory Database
Fix available
git-lfs fixed in 3.7.1
Oct 22, 2026 · GitHub Advisory Database
Updated
Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull c

Sources

CVE.orgVulnerability recordCVE-2025-26625
Official CVE identifier
cve.org
FIRST EPSSExploitation probabilityCVE-2025-26625
30-day exploitation probability 1.05%
first.org
EUVDVulnerability recordEUVD-2025-34886
Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbol
euvd.enisa.europa.eu
GitHub Advisory DatabasePackage advisoryGHSA-6pvw-g552-53c5
GitHub Advisory Database record mirrored by OSV.
github.com
NIST NVDVulnerability recordCVE-2025-26625
Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbol
nvd.nist.gov
OpenSSF OSV / OSV ScannerPackage advisoryBIT-git-lfs-2025-26625
Git LFS may write to arbitrary files via crafted symlinks
osv.dev

References

Freshness

Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

EUVDOct 23, 2026
GitHub Advisory DatabaseOct 23, 2026
OpenSSF OSV / OSV ScannerOct 23, 2026
FIRST EPSSOct 23, 2026
CVE.orgOct 21, 2026
NIST NVDOct 21, 2026

Priority score

14/100

Evidence confidence: High

A vendor or government advisory agrees with at least one other source.

Confirmed exploitation0/30
EPSS probability1/20
CVSS severity13/15
Public exploit0/10
Internet exposure0/10
Product prevalence0/5
Detection0/5
Threat research0/5

Decision signals

Four separate signals — do not infer one from another.

High

CVSS severity
8.6 v4.0
Technical impact. Separate from exploitation likelihood.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS probability
1.05% · p64.12%
Estimated probability of exploitation within 30 days (FIRST).
Known exploitation
No verified KEV listing
Evidence from CISA KEV or VulnCheck KEV only — not from EPSS alone.
Patch availability
Version ranges on file
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.

Weakness

CWE-59
Link Following
MITRE definition

Watch

A free account watches 5 technologies and gets a weekly digest. Professional adds immediate alerts.