Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-9751 | gitoxide does not detect SHA-1 collision attacks |
Github GHSA |
GHSA-2frx-2596-x5r6 | gitoxide does not detect SHA-1 collision attacks |
Fri, 23 Jan 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 23 Jan 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 04 Apr 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 04 Apr 2025 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | gitoxide does not detect SHA-1 collision attacks | |
| Weaknesses | CWE-328 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-23T17:08:57.443Z
Reserved: 2025-03-26T15:04:52.627Z
Link: CVE-2025-31130
Updated: 2025-04-04T14:51:41.104Z
Status : Deferred
Published: 2025-04-04T15:15:48.320
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-31130
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA