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.
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
- 31 Oct 2026, 15:18 UTC First seen by agentprime
- 31 Oct 2026, 15:18 UTC Confirmed by OSV