CVE-2025-26625: Github.com/git lfs/git lfs Git LFS May Write To Vulnerability

HIGH
Advisory Identifier: GHSA-6pvw-g552-53c5
CWE-59
Published
Advisory Summary

CVE-2025-26625 is a HIGH git lfs may write to vulnerability (CWE-59: Improper Link Resolution Before File Access ('Link Following')) affecting Github.com/git lfs/git lfs libraries in the Go ecosystem. The issue involves git lfs may write to arbitrary files via crafted symlinks. Remediation is available by upgrading affected packages to version 3.7.1.

CVE-2025-26625 at a Glance

CVE Identifier CVE-2025-26625
GHSA Identifier GHSA-6pvw-g552-53c5
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-59: Improper Link Resolution Before File Access ('Link Following')
Affected Product Github.com/git lfs/git lfs
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2025-26625

To remediate this vulnerability, upgrade all affected Github.com/git lfs/git lfs dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/git-lfs/git-lfs fixed: 3.7.1
Upgrade github.com/git-lfs/git-lfs to 3.7.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/git-lfs/git-lfs

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-26625, inspect your project dependencies for Github.com/git lfs/git lfs:

inspect dependencies for github.com/git-lfs/git-lfs

Analyze the terminal output to locate any version of Github.com/git lfs/git lfs in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.7.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following'), where the product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. In Github.com/git lfs/git lfs, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 - https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5 - https://nvd.nist.gov/vuln/detail/CVE-2025-26625 - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-26625 - https://github.com/git-lfs/git-lfs/releases/tag/v3.7.1 - [git-lfs/git-lfs@5c11ffce9a](https://github.com/git-lfs/git-lfs/commit/5c11ffce9a4f095ff356bc781e2a031abb46c1a8) - [git-lfs/git-lfs@0cffe93176](https://github.com/git-lfs/git-lfs/commit/0cffe93176b870055c9dadbb3cc9a4a440e98396) - [git-lfs/git-lfs@d02bd13f02](https://github.com/git-lfs/git-lfs/commit/d02bd13f02ef76f6807581cd6b34709069cb3615) ### 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](https://github.com/git-lfs/git-lfs/discussions). * For reports of additional vulnerabilities, please follow the Git LFS [security reporting policy](https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md).

CVE-2025-26625 Affected Github.com/git lfs/git lfs Versions

1 component(s)
Fixed Versions:
3.7.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/git-lfs/git-lfs
Go
≥ 0.5.2
< 3.7.1
3.7.1

References

Frequently Asked Questions

What is CVE-2025-26625?
CVE-2025-26625 is a security vulnerability in Github.com/git lfs/git lfs involving Git LFS may write to arbitrary files via crafted symlinks under CWE-59: Improper Link Resolution Before File Access ('Link Following').
Which Github.com/git lfs/git lfs versions are affected?
Affected versions include releases prior to 3.7.1 across affected packages: github.com/git-lfs/git-lfs.
What version fixes CVE-2025-26625?
Upgrading to 3.7.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/git-lfs/git-lfs affected?
Yes, github.com/git-lfs/git-lfs is affected in releases prior to 3.7.1. Upgrade your dependency to 3.7.1 or later.
What CWE is associated with CVE-2025-26625?
CVE-2025-26625 is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following') (The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.).
How can I check Go dependencies for CVE-2025-26625?
Run the dependency tree command: 'inspect dependencies for github.com/git-lfs/git-lfs'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6pvw-g552-53c5",
  "modified" : "2026-05-31T18:30:24Z",
  "published" : "2025-10-17T17:05:03Z",
  "aliases" : [ "CVE-2025-26625" ],
  "summary" : "Git LFS may write to arbitrary files via crafted symlinks",
  "details" : "### Impact\n\nWhen 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.\n\nGit 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.\n\nAs 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.\n\n### Patches\n\nThis problem exists in all versions since 0.5.2 and is patched in v3.7.1.  All users should upgrade to v3.7.1.\n\n### Workarounds\n\nSupport 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.\n\n### References\n\n- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5\n- https://nvd.nist.gov/vuln/detail/CVE-2025-26625\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-26625\n- https://github.com/git-lfs/git-lfs/releases/tag/v3.7.1\n- [git-lfs/git-lfs@5c11ffce9a](https://github.com/git-lfs/git-lfs/commit/5c11ffce9a4f095ff356bc781e2a031abb46c1a8)\n- [git-lfs/git-lfs@0cffe93176](https://github.com/git-lfs/git-lfs/commit/0cffe93176b870055c9dadbb3cc9a4a440e98396)\n- [git-lfs/git-lfs@d02bd13f02](https://github.com/git-lfs/git-lfs/commit/d02bd13f02ef76f6807581cd6b34709069cb3615)\n\n### For more information\n\nIf there are any questions or comments about this advisory:\n* For general questions, start a discussion in the Git LFS [discussion forum](https://github.com/git-lfs/git-lfs/discussions).\n* For reports of additional vulnerabilities, please follow the Git LFS [security reporting policy](https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md).",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/git-lfs/git-lfs"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.5.2"
      }, {
        "fixed" : "3.7.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.7.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-26625"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/git-lfs/git-lfs/commit/0cffe93176b870055c9dadbb3cc9a4a440e98396"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/git-lfs/git-lfs/commit/5c11ffce9a4f095ff356bc781e2a031abb46c1a8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/git-lfs/git-lfs/commit/d02bd13f02ef76f6807581cd6b34709069cb3615"
  }, {
    "type" : "WEB",
    "url" : "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-26625"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/git-lfs/git-lfs"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/git-lfs/git-lfs/releases/tag/v3.7.1"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2026/05/msg00055.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-59" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-17T17:05:03Z",
    "nvd_published_at" : "2025-10-17T16:15:37Z"
  }
}