{"ecosystem":"cargo","package":"hashbrown","version":null,"bugs":[{"id":4483,"ecosystem":"cargo","package_name":"hashbrown","affected_version":"0.15.0","fixed_version":"0.15.1","bug_id":"osv:GHSA-wwq9-3cpr-mm53","title":"Borsh serialization of HashMap is non-canonical","description":"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.\n\nThis can result in consensus splits and cause equivalent objects to be considered distinct.\n\nThis was patched in 0.15.1.","severity":"high","status":"fixed","source":"osv","source_url":"https://github.com/rust-lang/hashbrown/issues/576","labels":["RUSTSEC-2024-0402"],"created_at":"2026-04-26 03:01:01.428201+00:00","updated_at":"2026-04-26 03:01:01.428201+00:00"},{"id":4484,"ecosystem":"cargo","package_name":"hashbrown","affected_version":"0.15.0","fixed_version":"0.15.1","bug_id":"osv:RUSTSEC-2024-0402","title":"Borsh serialization of HashMap is non-canonical","description":"The borsh serialization of the HashMap did not follow the borsh specification.\nIt potentially produced non-canonical encodings dependent on insertion order.\nIt also did not perform canonicty checks on decoding.\n\nThis can result in consensus splits and cause equivalent objects to be\nconsidered distinct.\n\nThis was patched in 0.15.1.","severity":"medium","status":"fixed","source":"osv","source_url":"https://crates.io/crates/hashbrown","labels":["GHSA-wwq9-3cpr-mm53"],"created_at":"2026-04-26 03:01:01.430915+00:00","updated_at":"2026-04-26 03:01:01.430915+00:00"}],"total":2,"_cache":"hit"}