Rust advisories / crate
Security history · smallvec · data from Oct 24, 2026
Is smallvec safe to use? Its security history
VerdictNo open advisories. 4 past vulnerabilities were fixed; use 1.6.1 or newer to be clear of all of them.
5advisories on record
4vulnerabilities
0unmaintained notices
1.6.1newest fixed version
Every advisory, newest first
- Vulnerability CriticalRUSTSEC-2021-0003 · 2021-01-08Buffer overflow in SmallVec::insert_many
- Vulnerability CriticalRUSTSEC-2019-0012 · 2019-07-19Memory corruption in SmallVec::grow()
- Vulnerability CriticalRUSTSEC-2019-0009 · 2019-06-06Double-free and use-after-free in SmallVec::grow()
- UnsoundRUSTSEC-2018-0018 · 2018-09-25smallvec creates uninitialized value of any type
- Vulnerability CriticalRUSTSEC-2018-0003 · 2018-07-19Possible double free during unwinding in SmallVec::insert_many
Check your version
Run cargo tree -i smallvec to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
Download trends, dependents and alternatives: smallvec crate data.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Before you depend on itsmallvec crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?