Deps.rs

rust_decimal 1.36.0

[![dependency status](https://deps.rs/crate/rust_decimal/1.36.0/status.svg)](https://deps.rs/crate/rust_decimal/1.36.0)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate rust_decimal

Dependencies

(15 total, 3 outdated, 1 insecure)

CrateRequiredLatestStatus
 arbitrary^1.01.4.2up to date
 arrayvec^0.70.7.8up to date
 borsh^1.1.11.8.1up to date
 bytes^1.01.12.1up to date
 diesel^2.22.3.13up to date
 ndarray^0.15.60.17.2out of date
 num-traits^0.20.2.19up to date
 postgres-types^0.20.2.14up to date
 proptest^1.01.11.0up to date
 rand^0.80.10.3out of date
 rkyv ⚠️^0.7.420.8.18insecure
 rocket^0.5.0-rc.30.5.1up to date
 serde^1.01.0.229up to date
 serde_json^1.01.0.151up to date
 tokio-postgres^0.70.7.18up to date

Dev dependencies

(13 total, 3 outdated)

CrateRequiredLatestStatus
 bincode^1.03.0.0out of date
 bytes^1.01.12.1up to date
 criterion^0.50.8.2out of date
 csv^11.4.0up to date
 futures^0.30.3.34up to date
 postgres^0.190.19.14up to date
 rand^0.80.10.3out of date
 rust_decimal_macros^1.331.40.0up to date
 serde^1.01.0.229up to date
 serde_json^1.01.0.151up to date
 tokio^1.01.53.1up to date
 tokio-postgres^0.70.7.18up to date
 version-sync^0.90.9.5up to date

Security Vulnerabilities

rkyv: Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc

RUSTSEC-2026-0235

Shared pointer validation keyed already-validated pointees by their address and type, but did not include pointer metadata. For unsized pointees, an archive could therefore contain multiple Rc, Arc, or weak pointers that shared a data address but used different metadata, such as different slice lengths.

Once the first pointer had been validated, later pointers to the same address skipped pointee validation. The safe checked rkyv::access API could consequently return a slice with a forged length, allowing safe indexing to read out of bounds. The same validation bypass was reachable through checked deserialization with rkyv::from_bytes.

Version 0.8.17 includes pointer metadata in shared pointer validation and rejects conflicting metadata. The 0.7 series is also affected but is no longer supported by upstream. Users who process untrusted archives should upgrade to 0.8.17 or later.