Rust advisories / safe-transmute
Vulnerability CriticalRUSTSEC-2018-0013 · safe-transmute
RUSTSEC-2018-0013: Vec-to-vec transmutations could lead to heap overflow/corruption
Short answerA security vulnerability in the safe-transmute crate: Vec-to-vec transmutations could lead to heap overflow/corruption. Critical severity (CVSS 9.8). Fixed in 0.10.1: update to a fixed version.
| Crate | safe-transmute |
|---|---|
| Type | Vulnerability |
| Affected versions | From 0.4.0 before 0.10.1. |
| Fixed in | 0.10.1 |
| Severity | Critical, CVSS 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2018-11-27 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2018-21000, GHSA-2v78-j59h-fmpf |
What to do
- See which version you have:
cargo tree -i safe-transmute(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p safe-transmute. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplesafe-transmute = "0.10.1") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Affected versions of this crate switched the length and capacity arguments in the Vec::from_raw_parts() constructor, which could lead to memory corruption or data leakage.
The flaw was corrected by using the constructor correctly.
References
- Package: crates.io/crates/safe-transmute
- Advisory: rustsec.org/advisories/RUSTSEC-2018-0013.html
- Web: github.com/nabijaczleweli/safe-transmute-rs/pull/36
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?