Advisory

GHSA-vfvv-c25p-m7mm

Also known as: RUSTSEC-2026-0122

Summary

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

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-15 18:09 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

rkyv

crates.io · All systems

Affected

  • introduced 0.8.0, fixed 0.8.16 (semver)

Fixed versions

0.8.16

Fix

  • Fixed version 0.8.16
    cargo update -p rkyv --precise 0.8.16

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences