GHSA-4h96-mv53-2c86 — fast_id_map
GHSA-4h96-mv53-2c86 is a security vulnerability in fast_id_map. No vendor fix is recorded yet; mitigation options are listed below.
fast_id_map has a soundness issue and is unmaintained
Real-World Exposure
fast_id_mapReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
FastMap::get() lacks sufficient checks to its parameter index and is used to unsafely get a Vec element.
fast_id_map is unmaintained.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | fast_id_map | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast_id_map, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of fast_id_map has shipped for GHSA-4h96-mv53-2c86 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4h96-mv53-2c86 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4h96-mv53-2c86. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4h96-mv53-2c86 in your dependencies?
O3 Security finds GHSA-4h96-mv53-2c86 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.