CVE-2025-31130 | gitoxide does not detect SHA-1 collision attacks

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.

Published: 2025-04-04 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-31130 is rated Low Risk (31.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.21%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-31130

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.21% +0.18%
2 2026-05-13 0.06% 0.03% -0.03%
3 2026-01-29 — 0.06% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-31130

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 4.0 [email protected]

Weakness enumeration for CVE-2025-31130

GitHub Security Advisory for CVE-2025-31130

GHSA-2frx-2596-x5r6 · Severity: medium · Ecosystem: rust — gitoxide does not detect SHA-1 collision attacks

OS Trackers for CVE-2025-31130

vendor priority summary link
debian not yet assigned CVE-2025-31130 not yet assigned priority: Debian including 1 source packages (rust-gix-features), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2025-31130
ubuntu medium CVE-2025-31130 medium priority: Ubuntu including 1 source packages (rust-gix-features), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): needs-triage 3, DNE 2, ignored 2. https://ubuntu.com/security/CVE-2025-31130

Affected software / configurations for CVE-2025-31130

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-31130

cvelogic Threat Intelligence