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 hashbrown

Dependencies

(9 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.8.60.8.12up to date
 rustc-std-workspace-alloc^1.0.01.0.1up to date
 allocator-api2^0.2.90.4.0out of date
 compiler_builtins^0.1.20.1.160up to date
 rustc-std-workspace-core^1.0.01.0.1up to date
 equivalent^1.01.0.2up to date
 rayon^1.01.11.0up to date
 rkyv ⚠️^0.7.420.8.15out of date
 serde^1.0.251.0.228up to date

Dev dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bumpalo^3.13.03.20.2up to date
 doc-comment^0.3.10.3.4up to date
 fnv^1.0.71.0.7up to date
 lazy_static^1.41.5.0up to date
 rand^0.8.30.10.0out of date
 rayon^1.01.11.0up to date
 rkyv ⚠️^0.7.420.8.15out of date
 serde_test^1.01.0.177up 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.