# CVE-2024-47829: pnpm uses the md5 path shortening function causes packet paths to coincide, which causes indirect packet overwriting

> An MD5 collision in pnpm's path shortening can cause different packages to overwrite each other, leading to data corruption or potential supply chain risks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2025
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-8cc4-rfj6-fhg4, MINI-349m-cqm3-wrqj

## What is CVE-2024-47829?

CVE-2024-47829 is a medium-severity vulnerability in pnpm, published on 23 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pnpm is a package manager. Prior to version 10.0.0, the path shortening function uses the md5 function as a path shortening compression function, and if a collision occurs, it will result in the same storage path for two different libraries. Although the real names are under the package name /node_modoules/, there are no version numbers for the libraries they refer to. This issue has been patched in version 10.0.0.

Weakness: CWE-328 (Use of Weak Hash)

## Which versions are affected by CVE-2024-47829?

2 open source packages ship an affected version, including pnpm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pnpm` | npm | All versions | 10.0.0 |
| `pnpm` | npm | All versions | 10.0.0 |

Products: Pnpm Pnpm.

## How do I fix CVE-2024-47829?

Upgrade pnpm to 10.0.0 or later.

## Is CVE-2024-47829 being exploited?

There is no known exploitation of CVE-2024-47829 in the wild and no public exploit code.

## Other vulnerabilities in pnpm

- [CVE-2026-50016](https://insights.sbomify.com/CVE-2026-50016/): pnpm: Transitive dependency alias path traversal allows project path override via symlink replacement (high 8.8)
- [CVE-2026-55698](https://insights.sbomify.com/CVE-2026-55698/): pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes (high 8.8)
- [CVE-2025-69264](https://insights.sbomify.com/CVE-2025-69264/): pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default" (high 8.8)
- [CVE-2022-26183](https://insights.sbomify.com/CVE-2022-26183/): Untrusted Search Path in PNPM (high 8.8)
- [CVE-2026-59195](https://insights.sbomify.com/CVE-2026-59195/): pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47829 and fix it if it is affected.

What it is: CVE-2024-47829 is a medium-severity vulnerability in pnpm, published on 23 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47829 in the wild and no public exploit code.

Affected packages and fixed versions:
- pnpm (npm): affected all versions; fixed in 10.0.0
- pnpm (npm): affected all versions; fixed in 10.0.0

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/CVE-2024-47829/ (Markdown: https://insights.sbomify.com/CVE-2024-47829/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47829
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47829
- OSV: https://osv.dev/vulnerability/CVE-2024-47829

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47829/
Summaries are generated and may contain mistakes; the official description above is the record.