Deps.rs

nalgebra 0.34.1

[![dependency status](https://deps.rs/crate/nalgebra/0.34.1/status.svg)](https://deps.rs/crate/nalgebra/0.34.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 nalgebra

Dependencies

(24 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 alga^0.90.9.3up to date
 approx^0.50.5.1up to date
 bytemuck^1.51.25.0up to date
 defmt^1.0.11.0.1up to date
 encase^0.120.12.0up to date
 glam^0.300.31.0out of date
 matrixcompare-core^0.10.1.0up to date
 matrixmultiply^0.30.3.10up to date
 mint^0.50.5.9up to date
 nalgebra-macros^0.3.00.3.0up to date
 num-complex^0.40.4.6up to date
 num-rational^0.40.4.2up to date
 num-traits^0.20.2.19up to date
 pest^22.8.6up to date
 pest_derive^22.8.6up to date
 proptest^11.10.0up to date
 quickcheck^11.0.3up to date
 rand^0.90.9.2up to date
 rand_distr^0.50.5.1up to date
 rayon^1.61.11.0up to date
 rkyv ⚠️^0.7.410.8.14out of date
 serde^1.01.0.228up to date
 simba^0.90.9.1up to date
 typenum^1.121.19.0up to date

Dev dependencies

(8 total, 4 outdated)

CrateRequiredLatestStatus
 cool_asserts^2.0.32.0.4up to date
 criterion^0.40.8.2out of date
 itertools^0.130.14.0out of date
 matrixcompare^0.3.00.3.0up to date
 rand_isaac^0.40.5.0out of date
 rand_xorshift^0.40.5.0out of date
 serde_json^1.01.0.149up to date
 trybuild^1.0.901.0.115up 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.