Skip to content
OpenAdvisories
Medium GHSA-vfvv-c25p-m7mm RUSTSEC-2026-0122

rkyv: Panic safety bugs in `InlineVec::clear` and `SerVec::clear` enable arbitrary code execution

Published May 15, 2026 · Updated Sep 10, 2026 · Assigned by GHSA

Description

`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

- **CWE-415 (Double Free):** Heap corruption when element type holds `Box<T>`
- **CWE-416 (Use-After-Free):** Memory corruption when element reads from heap during `Drop`

Both vulnerabilities are triggerable entirely from safe Rust via `std::panic::catch_unwind` and require no special privileges.

Affected packages

EcosystemPackageAffectedFixedRecord
crates.io rkyv >= 0.8.0, < 0.8.16 0.8.16 GHSA-vfvv-c25p-m7mm

References