Email me

Rust advisories / rkyv

VulnerabilityRUSTSEC-2026-0235 · rkyv

RUSTSEC-2026-0235: Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc

Short answerA security vulnerability in the rkyv crate: Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc. No severity score was published. Fixed in 0.8.17: update to a fixed version.

Craterkyv
TypeVulnerability (memory-exposure)
Affected versionsFrom 0.7.0-pre.2 before 0.8.17.
Fixed in0.8.17
Severitynot scored
Published2026-05-13
Last changed2026-08-04
Also known asnone

What to do

  1. See which version you have: cargo tree -i rkyv (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p rkyv. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example rkyv = "0.8.17") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

Shared pointer validation keyed already-validated pointees by their address and type, but did not include pointer metadata. For unsized pointees, an archive could therefore contain multiple Rc, Arc, or weak pointers that shared a data address but used different metadata, such as different slice lengths.

Once the first pointer had been validated, later pointers to the same address skipped pointee validation. The safe checked rkyv::access API could consequently return a slice with a forged length, allowing safe indexing to read out of bounds. The same validation bypass was reachable through checked deserialization with rkyv::from_bytes.

Version 0.8.17 includes pointer metadata in shared pointer validation and rejects conflicting metadata. The 0.7 series is also affected but is no longer supported by upstream. Users who process untrusted archives should upgrade to 0.8.17 or later.

References

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for rkyv

Full security history of rkyv

Up next

Same craterkyv: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ