RUSTSEC-2026-0133 json
Invalid pointer arithmetic in `iter()` and `iter_mut()`
published 6mo ago modified 5mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Is RUSTSEC-2026-0133 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | auto_vec | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.