Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 11:13 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Exact source revision recorded 7 Nov 2026 01:31:20 UTC. It does not establish the source's current position. Latest evidence.

euvd · EUVD-2025-34886

Published

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.

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 17, 2025, 3:30:14 PM

dateUpdated: Oct 21, 2026, 10:07:30 AM

17 related source bulletins · separate from aliases

RHSA-2026:0204: Red Hat Security Advisory: git-lfs security update

CVE-2025-26625

WID-SEC-W-2025-2886: Red Hat Enterprise Linux (git-lfs, opentelemetry-collector): Mehrere Schwachstellen

CVE-2025-26625 · CVE-2025-68156

RHSA-2025:23648: Red Hat Security Advisory: ruby:3.3 security update

CVE-2025-24294 · CVE-2025-26625 · CVE-2025-58767

RHSA-2025:23744: security update for git-lfs

CVE-2025-26625

openSUSE-SU-2025:15710-1: govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media

CVE-2016-11063 · CVE-2016-11066 · CVE-2016-11067 · CVE-2016-11068 · CVE-2016-11069 · CVE-2016-11070 · CVE-2016-11071 · CVE-2016-11072 · CVE-2016-11073 · CVE-2016-11074 · CVE-2016-11075 · CVE-2016-11076 · CVE-2016-11077 · CVE-2016-11078 · CVE-2016-11079 · CVE-2016-11080 · CVE-2016-11081 · CVE-2016-11082 · CVE-2016-11083 · CVE-2016-11084 · CVE-2017-18872 · CVE-2023-32199 · CVE-2024-58269 · CVE-2025-10545 · CVE-2025-10678 · CVE-2025-10954 · CVE-2025-11374 · CVE-2025-11375 · CVE-2025-11579 · CVE-2025-11621 · CVE-2025-12044 · CVE-2025-26625 · CVE-2025-27093 · CVE-2025-41410 · CVE-2025-41443 · CVE-2025-54286 · CVE-2025-54287 · CVE-2025-54288 · CVE-2025-54289 · CVE-2025-54290 · CVE-2025-54291 · CVE-2025-54293 · CVE-2025-54469 · CVE-2025-54470 · CVE-2025-54471 · CVE-2025-54499 · CVE-2025-58073 · CVE-2025-58075 · CVE-2025-58356 · CVE-2025-59043 · CVE-2025-59048 · CVE-2025-59530 · CVE-2025-59836 · CVE-2025-59937 · CVE-2025-61141 · CVE-2025-61524 · CVE-2025-61581 · CVE-2025-61688 · CVE-2025-62156 · CVE-2025-62157 · CVE-2025-62375 · CVE-2025-62506 · CVE-2025-62513 · CVE-2025-62705 · CVE-2025-62714 · CVE-2025-62725 · CVE-2025-62820 · CVE-2025-64101 · CVE-2025-64102 · CVE-2025-64103

RHSA-2026:0203: Red Hat Security Advisory: git-lfs security update

CVE-2025-26625

RHSA-2026:0224: Red Hat Security Advisory: git-lfs security update

CVE-2025-26625

openSUSE-SU-2025:15643-1: git-lfs-3.7.1-1.1 on GA media

CVE-2025-26625

RHSA-2025:23927: Red Hat Security Advisory: ruby security update

CVE-2025-24294 · CVE-2025-26625 · CVE-2025-58767

RHSA-2026:0465: Red Hat Security Advisory: git-lfs security update

CVE-2025-26625

RHSA-2025:23667: security update for git-lfs

CVE-2025-26625

openSUSE-SU-2026:21621-1: Security update for git-lfs

CVE-2025-22869 · CVE-2025-26625

RHSA-2026:0459: Red Hat Security Advisory: git-lfs security update

CVE-2025-26625

RHSA-2026:0199: security update for git-lfs

CVE-2025-26625

RHSA-2025:23745: security update for git-lfs

CVE-2025-26625

RHSA-2026:0472: Red Hat Security Advisory: git-lfs security update

CVE-2025-26625

RHSA-2026:0460: Red Hat Security Advisory: git-lfs security update

CVE-2025-26625

Source published
Oct 17, 2025, 3:30:14 PM (timezone not stated)
Source modified
Oct 21, 2026, 10:07:30 AM (timezone not stated)
Observed here
7 Nov 2026 01:31:20 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.

EUVD 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

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 8 Nov 11:13 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current