RUSTSEC-2026-0127 Integer overflow in `array::ReadWrite::new()` leading to potential memory corruption
An integer overflow in a Rust library's array constructor can cause memory corruption, potentially leading to code execution or crashes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is RUSTSEC-2026-0127?
RUSTSEC-2026-0127 is a vulnerability in accessor, published on 2 May 2026.
Official description
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.
Which versions are affected by RUSTSEC-2026-0127?
1 open source package ship an affected version, including accessor.
| Package | Affected | Fixed in |
|---|---|---|
accessor crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2026-0127?
No fix has been published for RUSTSEC-2026-0127 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2026-0127 being exploited?
There is no known exploitation of RUSTSEC-2026-0127 in the wild and no public exploit code.