Medium severity · published Apr 4, 2025
CVE-2025-31130
gitoxide does not detect SHA-1 collision attacks
6.8
CVSS
0.3%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
None
Integrity
High
Availability
None
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 18% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GI
gitoxide · GitoxideLabs
< 0.42.0 · source: vendor
Affected product
GI
gitoxide
GitoxideLabs
More from gitoxide
7.8
CVE-2026-44471
gitoxide: Symlink prefix-reuse allows worktree escape during checkout
7.5
CVE-2026-82254
gitoxide before 0.69.0 Denial of Service via gix-pack
7.5
CVE-2026-82253
gitoxide before 0.82.0 Path Traversal via Submodule Name Validation Bypass
7.5
CVE-2026-82252
gitoxide before 0.52.1 Repository Boundary Violation via symlinked .gitmodules
7.5
CVE-2026-82251
gitoxide before 0.52.1 Path Traversal via Submodule Name