This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate peroxide

Dependencies

(22 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.102up to date
 arrow^5558.3.0out of date
 blas^0.220.23.0out of date
 csv^1.31.4.0up to date
 indexmap^12.14.0out of date
 json^0.120.12.4up to date
 lapack^0.190.20.0out of date
 matrixmultiply^0.30.3.10up to date
 netcdf^0.70.12.0out of date
 num-complex^0.40.4.6up to date
 order-stat^0.10.1.3up to date
 parquet^5558.3.0out of date
 paste^1.01.0.15up to date
 peroxide-ad^0.30.3.0up to date
 peroxide-num^0.10.1.4up to date
 puruspe^0.40.4.4up to date
 pyo3^0.27.10.28.3out of date
 rand^0.90.10.1out of date
 rand_distr^0.50.6.0out of date
 rayon^1.101.12.0up to date
 rkyv ⚠️^0.80.8.16maybe insecure
 serde^1.01.0.228up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.5.10.8.2out of date
 float-cmp^0.100.10.0up to date

Security Vulnerabilities

rkyv: Potential Undefined Behaviors in `Arc<T>`/`Rc<T>` impls of `from_value` on OOM

RUSTSEC-2026-0001

The SharedPointer::alloc implementation for sync::Arc<T> and rc::Rc<T> in rkyv/src/impls/alloc/rc/atomic.rs (and rc.rs) does not check if the allocator returns a null pointer on OOM (Out of Memory).

This null pointer can flow through to SharedPointer::from_value, which calls Box::from_raw(ptr) with the null pointer. This triggers undefined behavior when utilizing safe deserialization APIs (such as rkyv::from_bytes or rkyv::deserialize_using) if an OOM condition occurs during the allocation of the shared pointer.

The issue is reachable through safe code and violates Rust's safety guarantees.