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 glam

Dependencies

(12 total, 1 possibly insecure)

CrateRequiredLatestStatus
 approx^0.50.5.1up to date
 arbitrary^1.4.21.4.2up to date
 bytemuck^1.91.25.0up to date
 encase^0.120.12.0up to date
 libm^0.20.2.16up to date
 mint^0.5.80.5.9up to date
 rand^0.100.10.0up to date
 rkyv ⚠️^0.80.8.15maybe insecure
 serde_core^1.01.0.228up to date
 speedy^0.80.8.7up to date
 zerocopy^0.80.8.39up to date
 zerocopy-derive^0.80.8.39up to date

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.80.8.2up to date
 gungraun^0.170.17.2up to date
 rand_xoshiro^0.80.8.0up to date
 rkyv ⚠️^0.80.8.15maybe insecure
 serde_json^1.01.0.149up to date
 wasm-bindgen-test^0.3.00.3.63up 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.