← Back to CVE Explorer

CVE-2025-26625

Full vulnerability record from the local CVENow database.

Description

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.

Severity
HIGH
CVSS score
8.6 (v4.0)
Vulnerability status
Deferred
Source identifier
Published
2025-10-17 16:15:37.260000
Last modified
2026-10-21 10:16:53.207000
View original CVE JSON
{
  "id": "CVE-2025-26625",
  "sourceIdentifier": "[email protected]",
  "published": "2025-10-17T16:15:37.260",
  "lastModified": "2026-10-21T10:16:53.207",
  "vulnStatus": "Deferred",
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    },
    {
      "lang": "es",
      "value": "Git LFS es una extensión de Git para el control de versiones de archivos grandes. En las versiones de Git LFS de la 0.5.2 a la 3.7.0, al poblar el árbol de trabajo de un repositorio Git con el contenido de objetos Git LFS, ciertos comandos de Git LFS pueden escribir en archivos visibles fuera del árbol de trabajo de Git actual si existen enlaces simbólicos o duros que colisionan con las rutas de los archivos rastreados por Git LFS. Los comandos git lfs checkout y git lfs pull no verifican la existencia de enlaces simbólicos antes de escribir en archivos en el árbol de trabajo, permitiendo a un atacante crear un repositorio que contenga enlaces simbólicos o duros que hagan que Git LFS escriba en ubicaciones arbitrarias del sistema de archivos accesibles para el usuario que ejecuta estos comandos. Además, cuando los comandos git lfs checkout y git lfs pull se ejecutan en un repositorio bare, podrían escribir en archivos visibles fuera del repositorio. La vulnerabilidad está corregida en la versión 3.7.1. Como solución alternativa, el soporte para symlinks en Git puede deshabilitarse configurando la opción de configuración core.symlinks en false, después de lo cual las futuras clonaciones y recuperaciones no crearán enlaces simbólicos. Sin embargo, cualquier enlace simbólico o duro en los repositorios existentes aún proporcionará la oportunidad para que Git LFS escriba en sus destinos."
    }
  ],
  "affected": [
    {
      "source": "[email protected]",
      "affectedData": [
        {
          "vendor": "git-lfs",
          "product": "git-lfs",
          "versions": [
            {
              "version": ">= 0.5.2, < 3.7.1",
              "status": "affected"
            }
          ]
        }
      ]
    }
  ],
  "metrics": {
    "cvssMetricV40": [
      {
        "source": "[email protected]",
        "type": "Secondary",
        "cvssData": {
          "version": "4.0",
          "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
          "baseScore": 8.6,
          "baseSeverity": "HIGH",
          "attackVector": "NETWORK",
          "attackComplexity": "LOW",
          "attackRequirements": "NONE",
          "privilegesRequired": "NONE",
          "userInteraction": "PASSIVE",
          "vulnConfidentialityImpact": "HIGH",
          "vulnIntegrityImpact": "HIGH",
          "vulnAvailabilityImpact": "NONE",
          "subConfidentialityImpact": "NONE",
          "subIntegrityImpact": "NONE",
          "subAvailabilityImpact": "NONE",
          "exploitMaturity": "NOT_DEFINED",
          "confidentialityRequirement": "NOT_DEFINED",
          "integrityRequirement": "NOT_DEFINED",
          "availabilityRequirement": "NOT_DEFINED",
          "modifiedAttackVector": "NOT_DEFINED",
          "modifiedAttackComplexity": "NOT_DEFINED",
          "modifiedAttackRequirements": "NOT_DEFINED",
          "modifiedPrivilegesRequired": "NOT_DEFINED",
          "modifiedUserInteraction": "NOT_DEFINED",
          "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
          "modifiedVulnIntegrityImpact": "NOT_DEFINED",
          "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
          "modifiedSubConfidentialityImpact": "NOT_DEFINED",
          "modifiedSubIntegrityImpact": "NOT_DEFINED",
          "modifiedSubAvailabilityImpact": "NOT_DEFINED",
          "Safety": "NOT_DEFINED",
          "Automatable": "NOT_DEFINED",
          "Recovery": "NOT_DEFINED",
          "valueDensity": "NOT_DEFINED",
          "vulnerabilityResponseEffort": "NOT_DEFINED",
          "providerUrgency": "NOT_DEFINED"
        }
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "timestamp": "2025-10-17T15:44:04.948544Z",
          "id": "CVE-2025-26625",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "version": "2.0.3"
        }
      }
    ]
  },
  "weaknesses": [
    {
      "source": "[email protected]",
      "type": "Secondary",
      "description": [
        {
          "lang": "en",
          "value": "CWE-59"
        }
      ]
    }
  ],
  "references": [
    {
      "url": "https://github.com/git-lfs/git-lfs/commit/0cffe93176b870055c9dadbb3cc9a4a440e98396",
      "source": "[email protected]"
    },
    {
      "url": "https://github.com/git-lfs/git-lfs/commit/5c11ffce9a4f095ff356bc781e2a031abb46c1a8",
      "source": "[email protected]"
    },
    {
      "url": "https://github.com/git-lfs/git-lfs/commit/d02bd13f02ef76f6807581cd6b34709069cb3615",
      "source": "[email protected]"
    },
    {
      "url": "https://github.com/git-lfs/git-lfs/releases/tag/v3.7.1",
      "source": "[email protected]"
    },
    {
      "url": "https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5",
      "source": "[email protected]"
    },
    {
      "url": "https://lists.debian.org/debian-lts-announce/2026/05/msg00055.html",
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    },
    {
      "url": "https://lists.debian.org/debian-lts-announce/2026/10/msg00040.html",
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ]
}