Rust advisories / accessor
UnsoundRUSTSEC-2026-0127 · accessor
RUSTSEC-2026-0127: Integer overflow in `array::ReadWrite::new()` leading to potential memory corruption
Short answeraccessor has an API that can cause undefined behaviour from safe code: Integer overflow in `array::ReadWrite::new()` leading to potential memory corruption. No fixed version yet.
| Crate | accessor |
|---|---|
| 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 accessor. - Avoid the affected API, or replace the crate.
Details from the advisory
In array::ReadWrite::new() (line 83 of accessor/src/array.rs), let bytes = mem::size_of::<T>() * len can overflow usize when len is very large. In release mode, this silently wraps, potentially making bytes = 0. The mapper then maps with 0 bytes, and subsequent accesses (e.g. read_volatile_at) lead to undefined behavior or memory corruption.
Note: array::ReadWrite::new() itself is unsafe, so direct triggering requires an unsafe block. However, the integer overflow violates the implicit safety contract expected by callers and can lead to memory corruption downstream.
References
- Package: crates.io/crates/accessor
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0127.html
- Report: github.com/toku-sa-n/accessor/issues/49
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?