Deps.rs

half 2.7.1

[![dependency status](https://deps.rs/crate/half/2.7.1/status.svg)](https://deps.rs/crate/half/2.7.1)

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 half

Dependencies

(10 total, 1 possibly insecure)

CrateRequiredLatestStatus
 arbitrary^1.4.11.4.2up to date
 bytemuck^1.4.11.25.0up to date
 cfg-if^1.0.01.0.4up to date
 crunchy^0.2.20.2.4up to date
 num-traits^0.2.160.2.19up to date
 rand^0.9.00.9.2up to date
 rand_distr^0.5.00.5.1up to date
 rkyv ⚠️^0.8.00.8.14maybe insecure
 serde^1.01.0.228up to date
 zerocopy^0.8.260.8.39up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.50.8.2out of date
 crunchy^0.2.20.2.4up to date
 quickcheck^1.01.0.3up to date
 quickcheck_macros^1.01.1.0up to date
 rand^0.9.00.9.2up 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.