How severe is CVE-2025-26625?

No CVSS score has been assigned to CVE-2025-26625 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-26625?

CVE-2025-26625 affects the following packages: github.com/git-lfs/git-lfs (Go). Ecosystems affected: Go.

How do I fix CVE-2025-26625?

Update github.com/git-lfs/git-lfs to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-26625 is resolved across your whole dependency graph.

How do I detect CVE-2025-26625 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-26625 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-26625 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-26625 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-26625?

CVE-2025-26625 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-26625?

CVE-2025-26625 is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-26625 published, and has it been updated?

CVE-2025-26625 was published on October 17, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-26625 — git-lfs

Fix: git-lfs/git-lfs@0cffe93

CVE-2025-26625 is a CWE-59 vulnerability in github.com/git-lfs/git-lfs. A fix is available for github.com/git-lfs/git-lfs — see the affected versions and patch details below.

Git LFS may write to arbitrary files via crafted symlinks

Also known asBIT-git-lfs-2025-26625GHSA-6pvw-g552-53c5GO-2025-4038

Published

Oct 17, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-26625.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/git-lfs/git-lfs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

Git LFS has resolved this problem by revising the git lfs checkout and git lfs pull commands so that they check for symbolic links in the same manner as performed by Git before writing to files in the working tree. These commands now also remove existing files in the working tree before writing new files in their place.

As well, Git LFS has resolved a problem whereby the git lfs checkout and git lfs pull commands, when run in a bare repository, could write to files visible outside the repository. While a specific and relatively unlikely set of conditions were required for this to occur, it is no longer possible under any circumstances.

Patches

This problem exists in all versions since 0.5.2 and is patched in v3.7.1. All users should upgrade to v3.7.1.

Workarounds

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.

References

For more information

If there are any questions or comments about this advisory:

For general questions, start a discussion in the Git LFS discussion forum.
For reports of additional vulnerabilities, please follow the Git LFS security reporting policy.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/git-lfs/git-lfs`	≥ 0.5.2&&< 3.7.1	3.7.1`go get github.com/git-lfs/git-lfs@v3.7.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/git-lfs/git-lfs to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-26625 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability can cause Git LFS to write to arbitrary file system locations accessible to the user running git lfs checkout and git lfs pull. These commands are typically run by regular users without special access to system files, limiting the impact of this issue.

Workaround published by Red Hat

To prevent the creation of symbolic links when cloning or fetching a repository, the core.symlinks configuration option can be set to false, mitigating this vulnerability for new repositories. However, existing repositories containing symbolic or hard links are still vulnerable to this issue. Use the following command to set the core.symlinks configuration option to false: ~~~ git config --global core.symlinks false ~~~

Source: Red Hat security advisory for CVE-2025-26625 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`git-lfs-0:3.6.1-4.el10_1`	RHSA-2025:23667
Red Hat Enterprise Linux 10.0 Extended Update Support	`ruby-0:3.3.10-11.el10_0`	RHSA-2025:23927
Red Hat Enterprise Linux 10.0 Extended Update Support	`git-lfs-0:3.6.1-2.el10_0.1`	RHSA-2026:0224
Red Hat Enterprise Linux 8	`git-lfs-0:3.4.1-6.el8_10`	RHSA-2025:23745
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support	`git-lfs-0:2.13.3-3.el8_4.3`	RHSA-2026:0459
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support	`git-lfs-0:2.13.3-3.el8_6.5`	RHSA-2026:0465
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	`git-lfs-0:3.2.0-2.el8_8.5`	RHSA-2026:0460
Red Hat Enterprise Linux 9	`git-lfs-0:3.6.1-4.el9_7`	RHSA-2025:23744

Frequently Asked Questions

### Impact 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. Git LFS has resolved this problem by revising the `git lfs checkout` and `git lfs pull` commands so that they check for symbolic links in the same manner as performed by Git before writing to files in the working tree. These commands now also remove existing files in the working tree before writing new files in their pl

O3 Security · Impact-Aware SCA

Is CVE-2025-26625 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works