Git LFS may write to arbitrary files via crafted symlinks

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.6 · 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 · score source

EPSS

• CVE-2025-26625: 1.05% estimated exploitation activity in the next 30 days; percentile 64.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.…

Published by the source

17 Oct 2025, 17:05 UTC

Last modified by the source

31 May 2026, 18:30 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6pvw-g552-53c5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-26625

Advisory: Git LFS may write to arbitrary files via crafted symlinks
IDs: CVE-2025-26625, GHSA-6pvw-g552-53c5
Record: https://patchnext.com/advisories/cve-2025-26625 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/git-lfs/git-lfs 3.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/git-lfs/git-lfs: affected >= 0.5.2, <= 3.7.0; fixed in 3.7.1

## Suggested inspection (read-only)
- Go github.com/git-lfs/git-lfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/git-lfs/git-lfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6pvw-g552-53c5 (GitHub-reviewed advisory GHSA-6pvw-g552-53c5 lists affected ranges: Go github.com/git-lfs/git-lfs >=0.5.2 <=3.7.0)

Commands are suggestions: review each one before running it.