CVE-2025-31130
gitoxide is an implementation of git written in Rust. Before …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/GitoxideLabs/gitoxide/commit/f253f02a6658b3b7612a50d56c71f5ae4da4ca21
- github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-2frx-2596-x5r6
- nvd.nist.gov/vuln/detail/CVE-2025-31130
- rustsec.org/advisories/RUSTSEC-2025-0021.html
- github.com/advisories/GHSA-2frx-2596-x5r6
- nvd.nist.gov/vuln/detail/CVE-2025-31130
- cve.org/CVERecord?id=CVE-2025-31130
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.