Rust advisories / crate
Security history · rkyv · data from Oct 24, 2026
Is rkyv safe to use? Its security history
VerdictNo open advisories. 5 past vulnerabilities were fixed; use 0.8.17 or newer to be clear of all of them.
6advisories on record
5vulnerabilities
0unmaintained notices
0.8.17newest fixed version
Every advisory, newest first
- VulnerabilityRUSTSEC-2026-0235 · 2026-05-13Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc
- VulnerabilityRUSTSEC-2026-0233 · 2026-05-11Crafted archives can cause a use-after-free during deserialization
- VulnerabilityRUSTSEC-2026-0234 · 2026-05-11Insufficient archive validation can cause out-of-bounds reads in archives containing hash tables
- UnsoundRUSTSEC-2026-0122 · 2026-04-23Potential use-after-free due to lack of panic safety in `InlineVec::clear` and `SerVec::clear`
- VulnerabilityRUSTSEC-2026-0001 · 2026-01-05Potential Undefined Behaviors in `Arc<T>`/`Rc<T>` impls of `from_value` on OOM
- Vulnerability HighRUSTSEC-2021-0054 · 2021-04-28Archives may contain uninitialized memory
Check your version
Run cargo tree -i rkyv to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
Download trends, dependents and alternatives: rkyv crate data.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Before you depend on itrkyv crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?