rkyv
Affected
- introduced
0.8.0, fixed0.8.16(semver)
Fixed versions
0.8.16
Fix
- Fixed version
0.8.16cargo update -p rkyv --precise 0.8.16
Advisory
Also known as: RUSTSEC-2026-0122
rkyv: Panic safety bugs in InlineVec::clear and SerVec::clear enable arbitrary code execution
InlineVec::clear() and SerVec::clear() in rkyv were not panic-safe. Both functions iterate over their elements and call drop_in_place on each, updating self.len only *after* the loop. If an element's Drop implementation panics during the loop, self.len is left at its original value.
A subsequent invocation of clear() on the same container then re-visits the already-freed elements:
InlineVec::clear() is called again from InlineVec's own Drop implementation when the value is later dropped.SerVec::clear() is called again by SerVec::with_capacity() after the user closure returns.Technical Impact
Box<T> DropBoth vulnerabilities are triggerable entirely from safe Rust via std::panic::catch_unwind and require no special privileges.
Medium Basis: The source's own band: MODERATE
0.8.0, fixed 0.8.16 (semver)0.8.16
0.8.16cargo update -p rkyv --precise 0.8.16Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0