GHSA-4h96-mv53-2c86 json
fast_id_map has a soundness issue and is unmaintained
published last yr. modified last yr. also RUSTSEC-2025-0034
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
`FastMap::get()` lacks sufficient checks to its parameter index and is used to unsafely get a `Vec` element.
`fast_id_map` is unmaintained.
Is GHSA-4h96-mv53-2c86 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | fast_id_map | <=0.1.0 >=0.0.0-0 |
no fix listed |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/Bruce0203/fast_map
web
-
rustsec.org
/advisories/RUSTSEC-2025-0034.html
web, advisory
-
crates.io
/crates/fast_id_map
package
Sources
- GitHub Advisory GHSA-4h96-mv53-2c86
- OSV RUSTSEC-2025-0034
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.