Advisory record · RUSTSEC-2026-0252

Panic-safety unsoundness in `SplitVec::extend_from_slice` (uninitialized read)

No CVSS score

Published by OSV at 11 Aug 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
orx-split-veccrates.io>=0.0.0-0, <4.0.04.0.0
Identifiers
RUSTSEC-2026-0252
Published
11 Aug 2026
Updated
11 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

SplitVec in the orx-split-vec crate, versions before 4.0.0, is affected. If an element's Clone implementation panics during SplitVec::extend_from_slice, the vector's length is left counting slots that were never initialized, and later safe reads such as get, indexing, or iter can read those uninitialized slots. Upgrade to orx-split-vec 4.0.0 or later, which no longer commits the length before cloning elements.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:18 UTC First seen by agentprime
  2. 31 Oct 2026, 15:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.