Skip to content
Fencer Intel
medium 6.8

CVE-2025-31130 json

gitoxide does not detect SHA-1 collision attacks

published last yr. modified 15h ago also EUVD-2025-9751 , GHSA-2frx-2596-x5r6 , RUSTSEC-2025-0021

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. This vulnerability is fixed in 0.42.0.

Patch / fix

  • crates.io gix-features 0.41.0
  • crates.io gix-commitgraph 0.27.0
  • crates.io gix-index 0.39.0
  • crates.io gix-object 0.48.0
  • crates.io gix-odb 0.68.0
  • crates.io gix-pack 0.58.0
  • crates.io gitoxide 0.42.0
  • crates.io gitoxide-core 0.46.0
  • crates.io gix 0.71.0
  • crates.io gix-archive 0.20.0
  • crates.io gix-blame 0.1.0
  • crates.io gix-config 0.44.0
  • crates.io gix-diff 0.51.0
  • crates.io gix-dir 0.13.0
  • crates.io gix-discover 0.39.0
  • crates.io gix-filter 0.18.0
  • crates.io gix-fsck 0.10.0
  • crates.io gix-merge 0.4.0
  • crates.io gix-negotiate 0.19.0
  • crates.io gix-protocol 0.49.0
  • crates.io gix-ref 0.51.0
  • crates.io gix-revision 0.33.0
  • crates.io gix-revwalk 0.19.0
  • crates.io gix-status 0.18.0
  • crates.io gix-traverse 0.45.0
  • crates.io gix-worktree 0.40.0
  • crates.io gix-worktree-state 0.18.0
  • gitoxidelabs gitoxide 0.42.0
  • rust-gix-features Debian 14, Debian 13 0.39.1-2

debian advisories DEBIAN-CVE-2025-31130

  • gitoxide openSUSE Leap 16.0 0.56.0-bp160.1.1
  • gitoxide openSUSE Tumbleweed 0.42.0-1.1

opensuse advisories openSUSE-SU-2026:21558-1openSUSE-SU-2025:14994-1

Is CVE-2025-31130 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-2frx-2596-x5r6 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
OSV 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
crates.io gix-features
<0.41.0
>=0.0.0-0, <0.41.0
0.41.0
crates.io gix-commitgraph
<0.27.0
0.27.0
crates.io gix-index
<0.39.0
0.39.0
crates.io gix-object
<0.48.0
0.48.0
crates.io gix-odb
<0.68.0
0.68.0
crates.io gix-pack
<0.58.0
0.58.0
crates.io gitoxide
<0.42.0
0.42.0
crates.io gitoxide-core
<0.46.0
0.46.0
crates.io gix
<0.71.0
0.71.0
crates.io gix-archive
<0.20.0
0.20.0
crates.io gix-blame
<0.1.0
0.1.0
crates.io gix-config
<0.44.0
0.44.0
crates.io gix-diff
<0.51.0
0.51.0
crates.io gix-dir
<0.13.0
0.13.0
crates.io gix-discover
<0.39.0
0.39.0
crates.io gix-filter
<0.18.0
0.18.0
crates.io gix-fsck
<0.10.0
0.10.0
crates.io gix-merge
<0.4.0
0.4.0
crates.io gix-negotiate
<0.19.0
0.19.0
crates.io gix-protocol
<0.49.0
0.49.0
crates.io gix-ref
<0.51.0
0.51.0
crates.io gix-revision
<0.33.0
0.33.0
crates.io gix-revwalk
<0.19.0
0.19.0
crates.io gix-status
<0.18.0
0.18.0
crates.io gix-traverse
<0.45.0
0.45.0
crates.io gix-worktree
<0.40.0
0.40.0
crates.io gix-worktree-state
<0.18.0
0.18.0

Affected products

  • GitoxideLabs gitoxide

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.