RUSTSEC-2024-0435: Unsound usages of `Vec::from_raw_parts`

What to do

1. See which version you have: cargo tree -i fyrox-core (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p fyrox-core. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example fyrox-core = "0.36.0") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

The library provides a public safe API transmute_vec_as_bytes, which incorrectly assumes that any generic type T could have stable layout, causing to uninitialized memory exposure if the users pass any types with padding bytes as T and cast it to u8 pointer.

In the issue, we develop a PoC to show passing struct type to transmute_vec_as_bytes could lead to undefined behavior with Vec::from_raw_parts.

The developers provide a patch by changing trait of Copy to Pod, which can make sure T should be plain data. This was patched in the latest version of master branch, but still not on the latest release (0.28.1).

References

• Package: crates.io/crates/fyrox-core
• Advisory: rustsec.org/advisories/RUSTSEC-2024-0435.html
• Report: github.com/FyroxEngine/Fyrox/issues/630
• Web: github.com/FyroxEngine/Fyrox/pull/662

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.