Rust advisories / auto_vec
UnsoundRUSTSEC-2026-0133 · auto_vec
RUSTSEC-2026-0133: Invalid pointer arithmetic in `iter()` and `iter_mut()`
Short answerauto_vec has an API that can cause undefined behaviour from safe code: Invalid pointer arithmetic in `iter()` and `iter_mut()`. No fixed version yet.
| Crate | auto_vec |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-05-02 |
| Last changed | 2026-05-13 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i auto_vec. - Avoid the affected API, or replace the crate.
Details from the advisory
The iter() and iter_mut() APIs compute current = (&children[0] as *const *const RawAutoChild).sub(1), which performs pointer subtraction going before the start of the allocation. This is undefined behavior per Rust's pointer arithmetic rules.
This can be triggered through safe public APIs , iter() and iter_mut() , with no unsafe required from the caller.
References
- Package: crates.io/crates/auto_vec
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0133.html
- Report: github.com/lluvz/AutoVec/issues/1
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?