Deps.rs

rowanclarke / rs-remediate

[![dependency status](https://deps.rs/repo/github/rowanclarke/rs-remediate/status.svg)](https://deps.rs/repo/github/rowanclarke/rs-remediate)

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 remediate

Dependencies

(10 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 rand^0.8.50.9.2out of date
 pest^2.6.02.8.6up to date
 pest_derive^2.6.02.8.6up to date
 from-pest^0.3.20.3.4up to date
 pest-ast^0.3.30.3.6up to date
 bincode^1.3.33.0.0out of date
 serde^1.0.1641.0.228up to date
 rkyv ⚠️^0.7.420.8.14out of date
 num_enum^0.6.10.7.5out of date
 pathdiff^0.2.10.2.3up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 tempdir^0.3.70.3.7up to date
 once_cell^1.18.01.21.3up 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.