CVE-2025-31130

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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 v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
47
EG Risk 47/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

Published

April 4, 2025

Last Modified

April 15, 2026

References (3)

Affected Packages

(29 across 3 ecosystems)
crates.io(27)
PackageVulnerable rangeFix by version rangeDependents
gitoxide—
  • every version up to 0.42.0: fixed in 0.42.0
—
gitoxide-core—
  • every version up to 0.46.0: fixed in 0.46.0
—
gix—
  • every version up to 0.71.0: fixed in 0.71.0
—
gix-archive—
  • every version up to 0.20.0: fixed in 0.20.0
—
gix-blame—
  • every version up to 0.1.0: fixed in 0.1.0
—
gix-commitgraph—
  • every version up to 0.27.0: fixed in 0.27.0
—
gix-config—
  • every version up to 0.44.0: fixed in 0.44.0
—
gix-diff—
  • every version up to 0.51.0: fixed in 0.51.0
—
gix-dir—
  • every version up to 0.13.0: fixed in 0.13.0
—
gix-discover—
  • every version up to 0.39.0: fixed in 0.39.0
—
gix-features—
  • every version up to 0.41.0: fixed in 0.41.0
  • 0.0.0-0 up to 0.41.0: fixed in 0.41.0
—
gix-filter—
  • every version up to 0.18.0: fixed in 0.18.0
—
gix-fsck—
  • every version up to 0.10.0: fixed in 0.10.0
—
gix-index—
  • every version up to 0.39.0: fixed in 0.39.0
—
gix-merge—
  • every version up to 0.4.0: fixed in 0.4.0
—
gix-negotiate—
  • every version up to 0.19.0: fixed in 0.19.0
—
gix-object—
  • every version up to 0.48.0: fixed in 0.48.0
—
gix-odb—
  • every version up to 0.68.0: fixed in 0.68.0
—
gix-pack—
  • every version up to 0.58.0: fixed in 0.58.0
—
gix-protocol—
  • every version up to 0.49.0: fixed in 0.49.0
—
gix-ref—
  • every version up to 0.51.0: fixed in 0.51.0
—
gix-revision—
  • every version up to 0.33.0: fixed in 0.33.0
—
gix-revwalk—
  • every version up to 0.19.0: fixed in 0.19.0
—
gix-status—
  • every version up to 0.18.0: fixed in 0.18.0
—
gix-traverse—
  • every version up to 0.45.0: fixed in 0.45.0
—
gix-worktree—
  • every version up to 0.40.0: fixed in 0.40.0
—
gix-worktree-state—
  • every version up to 0.18.0: fixed in 0.18.0
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-gix-features—
  • every version up to 0.39.1-2: fixed in 0.39.1-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-gix-features—
  • every version up to 0.39.1-2: fixed in 0.39.1-2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-08 17:09 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-06 21:44 UTCOSV refresh
  5. 2026-10-06 15:16 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:24 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:02 UTCEPSS rescore
  11. 2026-09-29 15:19 UTCEPSS rescore
  12. 2026-09-28 13:50 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-26 00:24 UTCEPSS rescore
  16. 2026-09-26 00:24 UTCEPSS rescore
  17. 2026-09-24 14:02 UTCEPSS rescore
  18. 2026-09-23 13:47 UTCEPSS rescore
  19. 2026-09-20 20:15 UTCEPSS rescore
  20. 2026-09-18 19:27 UTCEPSS rescore
  21. 2026-09-17 03:20 UTCOSV refresh
  22. 2026-09-16 14:07 UTCEPSS rescore
  23. 2026-09-16 05:13 UTCEPSS rescore
  24. 2026-09-13 16:46 UTCEPSS rescore
  25. 2026-09-12 15:00 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:35 UTCEPSS rescore
  3. 2026-09-10 09:33 UTCEPSS rescore
  4. 2026-09-08 21:59 UTCEPSS rescore
  5. 2026-09-07 16:00 UTCEPSS rescore
  6. 2026-09-06 13:46 UTCEPSS rescore
  7. 2026-09-06 13:46 UTCEPSS rescore
  8. 2026-09-04 05:05 UTCEPSS rescore
  9. 2026-09-02 14:11 UTCEPSS rescore
  10. 2026-09-01 13:53 UTCEPSS rescore
  11. 2026-08-30 19:16 UTCEPSS rescore
  12. 2026-08-30 19:16 UTCEPSS rescore
  13. 2026-08-30 01:21 UTCEPSS rescore
  14. 2026-08-29 03:43 UTCOSV refresh
  15. 2026-08-28 21:40 UTCEPSS rescore
  16. 2026-08-27 14:24 UTCEPSS rescore
  17. 2026-08-26 14:45 UTCEPSS rescore
  18. 2026-08-25 13:48 UTCEPSS rescore
  19. 2026-08-24 14:16 UTCEPSS rescore
  20. 2026-08-23 00:18 UTCEPSS rescore
  21. 2026-08-21 23:48 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-18 13:47 UTCEPSS rescore
  24. 2026-08-17 13:46 UTCEPSS rescore
  25. 2026-08-16 14:55 UTCEPSS rescore
  26. 2026-08-16 02:13 UTCEPSS rescore
  27. 2026-08-15 01:29 UTCEPSS rescore
  28. 2026-08-13 21:59 UTCEPSS rescore
  29. 2026-08-12 15:20 UTCOSV refresh
  30. 2026-08-12 13:50 UTCEPSS rescore
  31. 2026-08-10 23:59 UTCEPSS rescore
  32. 2026-08-09 13:45 UTCEPSS rescore
  33. 2026-08-07 16:26 UTCEPSS rescore
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-05 19:16 UTCEPSS rescore
  36. 2026-08-04 15:09 UTCEPSS rescore
  37. 2026-08-04 10:37 UTCEPSS rescore
  38. 2026-08-03 10:35 UTCEPSS rescore
  39. 2026-08-02 02:26 UTCEPSS rescore
  40. 2026-08-01 04:15 UTCEPSS rescore
  41. 2026-07-30 16:27 UTCEPSS rescore
  42. 2026-07-30 01:29 UTCEPSS rescore
  43. 2026-07-28 15:35 UTCEPSS rescore
  44. 2026-07-27 22:54 UTCOSV refresh
  45. 2026-07-27 14:12 UTCEPSS rescore
  46. 2026-07-26 14:53 UTCEPSS rescore
  47. 2026-07-25 14:17 UTCEPSS rescore
  48. 2026-07-24 14:17 UTCEPSS rescore
  49. 2026-07-23 02:53 UTCEG score recompute
  50. 2026-07-22 14:07 UTCEPSS rescore
  51. 2026-07-22 14:07 UTCEPSS rescore
  52. 2026-07-21 15:24 UTCEPSS rescore
  53. 2026-07-21 15:24 UTCEPSS rescore
  54. 2026-07-20 17:07 UTCEPSS rescore
  55. 2026-07-19 14:30 UTCEPSS rescore
  56. 2026-07-19 14:30 UTCEPSS rescore
  57. 2026-07-19 02:28 UTCEPSS rescore
  58. 2026-07-19 02:28 UTCEPSS rescore
  59. 2026-07-18 10:04 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-16 17:02 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 01:59 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-13 22:29 UTCEPSS rescore
  67. 2026-07-13 06:12 UTCEPSS rescore
  68. 2026-07-13 06:12 UTCEPSS rescore
  69. 2026-07-12 05:46 UTCEPSS rescore
  70. 2026-07-12 05:46 UTCEPSS rescore
  71. 2026-07-11 08:27 UTCEPSS rescore
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-10 15:11 UTCOSV refresh
  74. 2026-07-09 19:09 UTCEPSS rescore
  75. 2026-07-08 15:14 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-31130?
CVE-2025-31130 is a medium vulnerability published on April 4, 2025. 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…
When was CVE-2025-31130 disclosed?
CVE-2025-31130 was first published on April 4, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-31130 actively exploited?
CVE-2025-31130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-31130?
CVE-2025-31130 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2025-31130?
A fix for CVE-2025-31130 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-31130

Explore →

Is Your Infrastructure Affected by CVE-2025-31130?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs