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.
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2025:23648 https://access.redhat.com/errata/RHSA-2025:23648
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2025:23667 https://access.redhat.com/errata/RHSA-2025:23667
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:23745 https://access.redhat.com/errata/RHSA-2025:23745
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:23744 https://access.redhat.com/errata/RHSA-2025:23744
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2025:23927 https://access.redhat.com/errata/RHSA-2025:23927
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:0199 https://access.redhat.com/errata/RHSA-2026:0199
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:0203 https://access.redhat.com/errata/RHSA-2026:0203
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2026:0204 https://access.redhat.com/errata/RHSA-2026:0204
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:0224 https://access.redhat.com/errata/RHSA-2026:0224
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2026:0460 https://access.redhat.com/errata/RHSA-2026:0460
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On Via RHSA-2026:0459 https://access.redhat.com/errata/RHSA-2026:0459
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions Red Hat Enterprise Linux 8.6 Telecommunications Update Service Via RHSA-2026:0465 https://access.redhat.com/errata/RHSA-2026:0465
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2026:0472 https://access.redhat.com/errata/RHSA-2026:0472