Vulnerability MediumRUSTSEC-2025-0137 · ruint
RUSTSEC-2025-0137: Unsoundness of safe `reciprocal_mg10`
Short answerA security vulnerability in the ruint crate: Unsoundness of safe `reciprocal_mg10`. GitHub rates it Medium. Fixed in 1.17.1: update to a fixed version.
| Crate | ruint |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 1.17.1. |
| Fixed in | 1.17.1 |
| Severity | Medium (GitHub rating) |
| Published | 2025-12-22 |
| Last changed | 2025-12-28 |
| Also known as | GHSA-9fjq-45qv-pcm7 |
| Affected functions | ruint::algorithms::div::reciprocal_mg10 |
What to do
- See which version you have:
cargo tree -i ruint(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p ruint. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleruint = "1.17.1") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
The function reciprocal_mg10 is marked as safe but can trigger undefined behavior (out-of-bounds access) because it relies on debug_assert! for safety checks instead of assert!.
When compiled in release mode, the debug_assert! is optimized out, potentially allowing invalid inputs to cause memory corruption.
References
- Package: crates.io/crates/ruint
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0137.html
- Report: github.com/recmo/uint/issues/550
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for ruint
Up next
Same crateruint: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?