How severe is GHSA-vfvv-c25p-m7mm?

No CVSS score has been assigned to GHSA-vfvv-c25p-m7mm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vfvv-c25p-m7mm?

GHSA-vfvv-c25p-m7mm affects the following packages: rkyv (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-vfvv-c25p-m7mm?

Update rkyv to 0.8.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfvv-c25p-m7mm is resolved across your whole dependency graph.

How do I detect GHSA-vfvv-c25p-m7mm in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rkyv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vfvv-c25p-m7mm if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

How does O3 Security protect against GHSA-vfvv-c25p-m7mm?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vfvv-c25p-m7mm can be triaged on real exposure rather than presence alone.

Is GHSA-vfvv-c25p-m7mm actively exploited in the wild?

No public exploit code has been indexed for GHSA-vfvv-c25p-m7mm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vfvv-c25p-m7mm published, and has it been updated?

GHSA-vfvv-c25p-m7mm was published on May 15, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-vfvv-c25p-m7mm — rkyv

Fix: rkyv/rkyv@5828cf5

GHSA-vfvv-c25p-m7mm is a remote code execution vulnerability in rkyv. A fix is available for rkyv — see the affected versions and patch details below.

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

Also known asRUSTSEC-2026-0122

Published

May 15, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀rkyv

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rkyv`	≥ 0.8.0&&< 0.8.16	0.8.16`cargo update -p rkyv --precise 0.8.16`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rkyv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rkyv to 0.8.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfvv-c25p-m7mm is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vfvv-c25p-m7mm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vfvv-c25p-m7mm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`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

O3 Security · Impact-Aware SCA

Is GHSA-vfvv-c25p-m7mm in your dependencies?

O3 Security finds GHSA-vfvv-c25p-m7mm across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works