Reversible One-Way Hash Affecting cargo-c package, versions <0.10.23-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.22% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-WOLFILATEST-CARGOC-15375787
  • published4 Mar 2026
  • disclosed4 Apr 2025

Introduced: 4 Apr 2025

CVE-2025-31130  (opens in a new tab)
CWE-328  (opens in a new tab)

How to fix?

Upgrade Wolfi cargo-c to version 0.10.23-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cargo-c package and not the cargo-c package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

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.