Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisory

Rust rkyv Flaws Let Malicious Archives Trigger Memory Safety Errors

Vulnerability Disclosure · 4 sources · Updated 4mo ago · First seen Aug 4, 2026

Rust rkyv Flaws Let Malicious Archives Trigger Memory Safety Errors

Multiple vulnerabilities in the Rust serialization crate rkyv allow crafted untrusted archives to bypass validation in supposedly safe checked deserialization paths and trigger memory safety failures. RustSec advisories RUSTSEC-2026-0233, RUSTSEC-2026-0234, and RUSTSEC-2026-0235 describe flaws that can lead to a heap use-after-free in ArchivedString::deserialize, out-of-bounds reads in archives containing hash tables, and out-of-bounds reads involving Rc/Arc shared pointers. Affected safe APIs include rkyv::access and rkyv::from_bytes, and the resulting impact includes process crashes, denial of service, and potential memory exposure when applications process attacker-controlled archive bytes.

The issues were fixed in rkyv 0.8.17, which strengthens archive range validation, rejects malformed relative pointers and inconsistent hash table states, and hardens shared-pointer verification. An upstream code change shows the project now validates shared pointers using both erased data pointers and pointer metadata, explicitly detecting conflicting metadata such as forged slice lengths that reference the same memory region. The maintainers said the 0.7 series is also affected but unsupported, and advised users handling untrusted archives to upgrade to 0.8.17 or later.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · May 11, 2026 – Aug 4, 2026
  1. Aug 4, 20264mo ago

    RustSec publishes three rkyv vulnerability advisories

    RustSec issued advisories for three distinct rkyv flaws: a use-after-free during deserialization, out-of-bounds reads involving hash tables, and out-of-bounds reads involving Rc/Arc validation. The advisories state that rkyv 0.8.17 fixes the issues and recommend upgrading when processing untrusted archives.

    RUSTSEC-2026-0233: rkyv: Crafted archives can cause a use-after-free during deserialization › RustSec Advisory Database
  2. Jul 2, 20265mo ago

    rkyv commits shared-pointer metadata validation fix

    A code commit updated rkyv validation to track erased pointer metadata for shared pointers and detect metadata mismatches, addressing the Rc/Arc validation issue and related unsafe archive handling.

    Check shared pointer metadata during validation · rkyv/rkyv@3c9d07f · GitHub
  3. May 13, 20266mo ago

    rkyv Rc/Arc validation flaw reported

    A vulnerability affecting rkyv shared-pointer validation was reported, showing that conflicting metadata on Rc/Arc-style pointers could bypass validation and enable out-of-bounds reads through safe APIs.

    RUSTSEC-2026-0235: rkyv: Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc › RustSec Advisory Database
  4. May 11, 20266mo ago

    rkyv hash-table validation flaw reported

    A second rkyv vulnerability was reported involving malformed relative pointers and invalid ArchivedHashTable states that could later cause out-of-bounds reads, memory exposure, or denial of service.

    RUSTSEC-2026-0234: rkyv: Insufficient archive validation can cause out-of-bounds reads in archives containing hash tables › RustSec Advisory Database
  5. May 11, 20266mo ago

    rkyv use-after-free vulnerability reported

    A vulnerability in rkyv's archive range validation was reported, describing how a crafted archive could lead to an invalid pointer reaching string deserialization and trigger a heap use-after-free.

    RUSTSEC-2026-0233: rkyv: Crafted archives can cause a use-after-free during deserialization › RustSec Advisory Database
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.