Rust advisories / binary_vec_io
Unsound HighRUSTSEC-2025-0109 · binary_vec_io
RUSTSEC-2025-0109: Out-of-bounds memory access in binary_read_to_ref and binary_write_from_ref
Short answerbinary_vec_io has an API that can cause undefined behaviour from safe code: Out-of-bounds memory access in binary_read_to_ref and binary_write_from_ref. No fixed version yet.
| Crate | binary_vec_io |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | High (GitHub rating) |
| Published | 2025-10-21 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-wwxp-hxh6-8gf8 |
| Affected functions | binary_vec_io::binary_read_to_ref, binary_vec_io::binary_write_from_ref |
What to do
- Find who pulls it in:
cargo tree -i binary_vec_io. - Avoid the affected API (
binary_vec_io::binary_read_to_ref,binary_vec_io::binary_write_from_ref), or replace the crate.
Details from the advisory
Safe functions accept a single &T or &mut T but multiply by n to create slices extending beyond allocated memory when n > 1.
These functions use from_raw_parts to create slices larger than the underlying allocation, violating memory safety.
The binary_vec_io repository is archived and unmaintained.
References
- Package: crates.io/crates/binary_vec_io
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0109.html
- Web: github.com/RustSec/advisory-db/pull/2428
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?