Rust advisories / hivex
Unsound MediumRUSTSEC-2026-0029 · hivex
RUSTSEC-2026-0029: Double-free and use-after-free for Hive
Short answerhivex has an API that can cause undefined behaviour from safe code: Double-free and use-after-free for Hive. Fixed in 0.2.1.
| Crate | hivex |
|---|---|
| Type | Unsound |
| Affected versions | Before 0.2.1. |
| Fixed in | 0.2.1 |
| Severity | Medium (GitHub rating) |
| Published | 2026-02-26 |
| Last changed | 2026-03-01 |
| Also known as | GHSA-j8cj-hw74-64jv |
| Affected functions | hivex::Hive::close, hivex::Hive::from_handle |
What to do
- See which version you have:
cargo tree -i hivex(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p hivex. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplehivex = "0.2.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
Drop implementation for Hive did perform free, but so did Hive::close, which, at the end of the scope performed Drop, therefore triggering double-free.
Additionally, function Hive::from_handle was not marked as unsafe, making it, in combination with as_handle easy to clone and trigger double-free in safe code or triggering UB when using invalid pointer.
References
- Package: crates.io/crates/hivex
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0029.html
- Web: codeberg.org/1millibyte/toolsnt/issues/18
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?