https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T19:52:03.884821+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/alsa-2025:23667 ALSA-2025:23667 — Important: git-lfs security update 2026-10-03T19:52:04.225914+00:00

Affected: AlmaLinux:10: git-lfs

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server.

Security Fix(es):

* git-lfs: Git LFS may write to arbitrary files via crafted symlinks (CVE-2025-26625)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

 https://cve.radiocsirt.org/vuln/bdu:2025-13253 bdu:2025-13253 2026-10-03T19:52:04.225976+00:00 bdu:2025-13253 https://cve.radiocsirt.org/vuln/euvd-2026-323200 EUVD-2026-323200 2026-10-03T19:52:04.225993+00:00 EUVD-2026-323200 https://cve.radiocsirt.org/vuln/fkie_cve-2025-26625 fkie_cve-2025-26625 2026-10-03T19:52:04.226004+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-6pvw-g552-53c5 GHSA-6pvw-g552-53c5 — Git LFS may write to arbitrary files via crafted symlinks 2026-10-03T19:52:04.226034+00:00

Affected: Go: github.com/git-lfs/git-lfs

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

 https://cve.radiocsirt.org/vuln/oesa-2026-4067 OESA-2026-4067 — git-lfs security update 2026-10-03T19:52:04.226077+00:00

Affected: openEuler:24.03-LTS-SP3: git-lfs

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server. Security Fix(es):

Processing an incomplete post-handshake message for a QUIC connection can cause a panic.(CVE-2023-39321)

QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size.(CVE-2023-39322)

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.(CVE-2025-22874)

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

 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15643-1 openSUSE-SU-2025:15643-1 — git-lfs-3.7.1-1.1 on GA media 2026-10-03T19:52:04.226154+00:00

git-lfs-3.7.1-1.1 on GA media

 https://cve.radiocsirt.org/vuln/rhsa-2025:23927 RHSA-2025:23927 — Red Hat Security Advisory: ruby security update 2026-10-03T19:52:04.226172+00:00

resolv: Denial of Service in resolv gem git-lfs: Git LFS may write to arbitrary files via crafted symlinks rexml: REXML denial of service

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-26625 UBUNTU-CVE-2025-26625 2026-10-03T19:52:04.226191+00:00

Affected: Ubuntu:Pro:18.04:LTS: git-lfs, Ubuntu:Pro:20.04:LTS: git-lfs, Ubuntu:22.04:LTS: git-lfs, Ubuntu:Pro:24.04:LTS: git-lfs, Ubuntu:25.10: git-lfs

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.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2886 WID-SEC-W-2025-2886 — Red Hat Enterprise Linux (git-lfs, opentelemetry-collector): Mehrere Schwachstellen 2026-10-03T19:52:04.226224+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren und einen Denial-of-Service-Zustand zu verursachen.