Rust advisories / fast_id_map
Unsound MediumRUSTSEC-2025-0034 · fast_id_map
RUSTSEC-2025-0034: soundness issue and unmaintained
Short answerfast_id_map has an API that can cause undefined behaviour from safe code: soundness issue and unmaintained. No fixed version yet.
| Crate | fast_id_map |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Medium (GitHub rating) |
| Published | 2025-05-06 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-4h96-mv53-2c86 |
| Affected functions | fast_id_map::FastMap::get |
What to do
- Find who pulls it in:
cargo tree -i fast_id_map. - Avoid the affected API (
fast_id_map::FastMap::get), or replace the crate.
Details from the advisory
FastMap::get() lacks sufficient checks to its parameter index and is used to unsafely get a Vec element.
fast_id_map is unmaintained.
References
- Package: crates.io/crates/fast_id_map
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0034.html
- Web: github.com/Bruce0203/fast_map
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?