Vulnerability HighRUSTSEC-2024-0402 · hashbrown
RUSTSEC-2024-0402: Borsh serialization of HashMap is non-canonical
Short answerA security vulnerability in the hashbrown crate: Borsh serialization of HashMap is non-canonical. GitHub rates it High. Fixed in 0.15.1: update to a fixed version.
| Crate | hashbrown |
|---|---|
| Type | Vulnerability |
| Affected versions | From 0.15.0 before 0.15.1. |
| Fixed in | 0.15.1 |
| Severity | High (GitHub rating) |
| Published | 2024-10-11 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-wwq9-3cpr-mm53 |
| Affected functions | hashbrown::HashMap::borsh_serialize |
What to do
- See which version you have:
cargo tree -i hashbrown(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p hashbrown. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplehashbrown = "0.15.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
The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.
This can result in consensus splits and cause equivalent objects to be considered distinct.
This was patched in 0.15.1.
References
- Package: crates.io/crates/hashbrown
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0402.html
- Report: github.com/rust-lang/hashbrown/issues/576
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
Same cratehashbrown: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?