Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-26625: Git LFS may write to arbitrary files via crafted symlinks

Noroxi assessment

Priority: Monitor (action score 34/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 64.6% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: git-lfs git-lfs 3.7.1.

Low priority for now. Upgrade to git-lfs git-lfs 3.7.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.6 · v4.0—No exploit Fix available
Published
Oct 17, 2025
Updated
Oct 21, 2026
EPSS
1.0% · 64th percentile

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.0%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
8.6
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-26625

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for git-lfs records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • git-lfs git-lfs

    • >= 0.5.2, < 3.7.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10git-lfsbefore 3.6.1-4.el10_13.6.1-4.el10_1
AlmaLinux:8git-lfsbefore 3.4.1-6.el8_103.4.1-6.el8_10
AlmaLinux:9git-lfsbefore 3.6.1-4.el9_73.6.1-4.el9_7
Alpine:v3.23git-lfsbefore 3.7.1-r03.7.1-r0
Debian:12git-lfsbefore 3.3.0-1+deb12u23.3.0-1+deb12u2
Debian:13git-lfsbefore 3.6.1-1+deb13u13.6.1-1+deb13u1
Debian:14git-lfsbefore 3.7.1-13.7.1-1
Gogithub.com/git-lfs/git-lfsfrom 0.5.2 · before 3.7.13.7.1
Gogithub.com/git-lfs/git-lfsfrom 0.5.2—
Gogithub.com/git-lfs/git-lfs/v3before 3.7.13.7.1
openSUSE:Leap 16.0git-lfsbefore 3.7.1-bp160.1.13.7.1-bp160.1.1
openSUSE:Tumbleweedgit-lfsbefore 3.7.1-1.13.7.1-1.1
Red Hat:enterprise_linux_eus:10.0git-lfsbefore 0:3.6.1-2.el10_0.10:3.6.1-2.el10_0.1
Red Hat:enterprise_linux_eus:10.0git-lfs-debuginfobefore 0:3.6.1-2.el10_0.10:3.6.1-2.el10_0.1
Red Hat:enterprise_linux_eus:10.0git-lfs-debugsourcebefore 0:3.6.1-2.el10_0.10:3.6.1-2.el10_0.1
Red Hat:enterprise_linux_eus:10.0rubybefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-bundled-gemsbefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-bundled-gems-debuginfobefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-debuginfobefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-debugsourcebefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-default-gemsbefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-develbefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-docbefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0
Red Hat:enterprise_linux_eus:10.0ruby-libsbefore 0:3.3.10-11.el10_00:3.3.10-11.el10_0

+96

Same product

git-lfs: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-53263Git LFS permits exfiltration of credentials via crafted HTTP URLs
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
git-lfs git-lfs3.7.1 · descriptionVendor (CNA)
almalinux:git-lfs3.6.1-4.el10_1 · AlmaLinux:10Package registry (OSV)
alpine:git-lfs3.7.1-r0 · Alpine:v3.23Package registry (OSV)
debian:git-lfs3.3.0-1+deb12u2 · Debian:12Package registry (OSV)
debian:git-lfs3.6.1-1+deb13u1 · Debian:13Package registry (OSV)
Go:github.com/git-lfs/git-lfs3.7.1Package registry (OSV)
Go:github.com/git-lfs/git-lfs/v33.7.1Package registry (OSV)
opensuse:git-lfs3.7.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:ruby0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-bundled-gems0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-bundled-gems-debuginfo0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-debuginfo0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-debugsource0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-default-gems0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-devel0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-doc0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-libs0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:ruby-libs-debuginfo0:3.3.10-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:rubygem-bigdecimal0:3.1.5-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:rubygem-bigdecimal-debuginfo0:3.1.5-5.module+el9.6.0+23780+e40d2335 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
rocky linux:git-lfs0:3.6.1-4.el10_1 · Rocky Linux:10Package registry (OSV)
suse:git-lfs3.7.1-150600.13.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
P
Scope
X

Weakness class (CWE)

CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records