🛡️ RUSTSEC-2025-0166 — stackvector
Description
Multiple soundness issues in stackvector
Affected versions of stackvector contained multiple soundness issues that could allow safe Rust code to trigger undefined behavior.
One issue was that StackVec::length was exposed as a public field. Safe Rust code could set length to a value larger than the backing array capacity. Other safe methods, including remove, pop, and truncate, relied on length before performing unsafe pointer operations (ptr::read, ptr::copy, offset/add). If length was corrupted by safe code, these methods could perform out-of-bounds pointer arithmetic, reads, writes, or copies.
The upstream maintainer also identified additional soundness issues, including the use of mem::uninitialized in StackVec::from_vec_unchecked, which was reachable through from_vec, and Miri violations related to MaybeUninit usage.
Version 2.0.0 was released to fix the known soundness issues.
Affected software
RUSTSEC-2025-0166 is recorded against 1 package.
- stackvector
Timeline and source
Published on 23 October 2025 and last revised on 2 July 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
crates.io (Package)
rustsec.org (Advisory)
github.com (Report)
github.com (Web)
github.com (Web)
github.com (Report)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| stackvector | — | — |
References
Similar Threats
- High CVE-2021-29939
More RUSTSEC 2025 advisories
Browse all of RUSTSEC 2025 in the advisory index.
Free Vulnerability Check
Is your site affected by RUSTSEC-2025-0166?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against RUSTSEC-2025-0166 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.