Rust advisories / totally-safe-transmute
UnsoundRUSTSEC-2025-0030 · totally-safe-transmute
RUSTSEC-2025-0030: totally-safe-transmute allows transmuting any type to any other type in safe Rust
Short answertotally-safe-transmute has an API that can cause undefined behaviour from safe code: totally-safe-transmute allows transmuting any type to any other type in safe Rust. No fixed version yet.
| Crate | totally-safe-transmute |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2025-02-10 |
| Last changed | 2025-05-06 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i totally-safe-transmute. - Avoid the affected API, or replace the crate.
Details from the advisory
This crate is a toy and should never be used.
It showcases a known soundness issue (https://github.com/rust-lang/rust/issues/32670) that will never get fixed. In short, Linux provides a file called /proc/self/mem which can be used by a program to modify its own memory. This library modifies an enum variant number by accessing its own memory as a file to effectively transmute a variable.
See also <https://doc.rust-lang.org/std/os/unix/io/index.html#procselfmem-and-similar-os-features>
References
- Package: crates.io/crates/totally-safe-transmute
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0030.html
- Web: github.com/ben0x539/totally-safe-transmute
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?