Deps.rs

glamx 0.3.0

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 glamx

Dependencies

(8 total, 1 possibly insecure)

CrateRequiredLatestStatus
 approx^0.50.5.1up to date
 bytemuck^11.25.0up to date
 glam^0.330.33.2up to date
 nalgebra^0.350.35.0up to date
 num-traits^0.20.2.19up to date
 rkyv ⚠️^0.80.8.17maybe insecure
 serde^1.01.0.228up to date
 simba^0.100.10.0up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 approx^0.50.5.1up to date
 glam^0.330.33.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.