# GHSA-4h96-mv53-2c86: soundness issue and unmaintained

> Unmaintained Rust library allows memory corruption via unsafe index access, potentially leading to code execution or crashes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2025
- **Also known as:** RUSTSEC-2025-0034

## What is GHSA-4h96-mv53-2c86?

GHSA-4h96-mv53-2c86 is a memory corruption vulnerability in fast_id_map, published on 6 May 2025. 

### Official description

`FastMap::get()` lacks sufficient checks to its parameter index and is used to unsafely get a `Vec` element.

`fast_id_map` is unmaintained.

## Which versions are affected by GHSA-4h96-mv53-2c86?

3 open source packages ship an affected version, including fast_id_map.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fast_id_map` | crates.io | All versions to 0.1.0 | None |
| `fast_id_map` | crates.io | All versions to 0.1.0 | None |
| `fast_id_map` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-4h96-mv53-2c86?

No fix has been published for GHSA-4h96-mv53-2c86 yet. Limit exposure of the affected software until one is available.

## Is GHSA-4h96-mv53-2c86 being exploited?

There is no known exploitation of GHSA-4h96-mv53-2c86 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4h96-mv53-2c86 and fix it if it is affected.

What it is: GHSA-4h96-mv53-2c86 is a memory corruption vulnerability in fast_id_map, published on 6 May 2025. 
Exploitation: There is no known exploitation of GHSA-4h96-mv53-2c86 in the wild and no public exploit code.

Affected packages and fixed versions:
- fast_id_map (crates.io): affected all versions up to 0.1.0; no fix listed
- fast_id_map (crates.io): affected all versions up to 0.1.0; no fix listed
- fast_id_map (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4h96-mv53-2c86/ (Markdown: https://insights.sbomify.com/GHSA-4h96-mv53-2c86/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4h96-mv53-2c86

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4h96-mv53-2c86/
Summaries are generated and may contain mistakes; the official description above is the record.