Reversible One-Way Hash Affecting cargo-c package, versions <0.10.23-r1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-CHAINGUARDLATEST-CARGOC-14885708
- published7 Jan 2026
- disclosed4 Apr 2025
Introduced: 4 Apr 2025
CVE-2025-31130 (opens in a new tab)How to fix?
Upgrade Chainguard 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 Chainguard.
See How to fix? for Chainguard 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.