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 korrosync

Dependencies

(20 total, 1 possibly insecure)

CrateRequiredLatestStatus
 argon2^0.5.30.5.3up to date
 axum^0.8.60.8.8up to date
 axum-extra^0.12.10.12.5up to date
 axum-server^0.8.00.8.0up to date
 rkyv ⚠️^0.80.8.14maybe insecure
 chrono^0.4.420.4.43up to date
 color-eyre^0.6.50.6.5up to date
 governor^0.100.10.4up to date
 redb^3.1.03.1.0up to date
 serde^1.0.2281.0.228up to date
 serde_json^1.0.1451.0.149up to date
 thiserror^2.02.0.18up to date
 tokio^1.48.01.49.0up to date
 tokio-util^0.70.7.18up to date
 tower^0.50.5.3up to date
 tower-http^0.6.60.6.8up to date
 tower_governor^0.8.00.8.0up to date
 tracing^0.1.410.1.44up to date
 tracing-subscriber^0.3.200.3.22up to date
 uuid^1.18.11.20.0up to date

Dev dependencies

(7 total, 1 outdated)

CrateRequiredLatestStatus
 assert_cmd^2.1.12.1.2up to date
 reqwest^0.13.00.13.1up to date
 tokio-retry2^0.7.00.9.1out of date
 tokio^1.48.01.49.0up to date
 tempfile^3.23.03.24.0up to date
 temp-env^0.3.60.3.6up to date
 serial_test^3.2.03.3.1up 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.