# CVE-2026-82392: pnpm: Virtual store linker path traversal via unvalidated depPath name in lockfileToDepGraph

> Attackers can write files outside node_modules via malicious lockfiles, potentially executing code if build scripts are enabled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-c59q-g84q-2gj5, MINI-q5hw-43wp-pc9v

## What is CVE-2026-82392?

CVE-2026-82392 is a high-severity path traversal vulnerability in pnpm, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

pnpm is a package manager. Prior to 10.34.5 and from 11.0.0 until 11.11.0, pnpm parses the package name from attacker-controlled pnpm-lock.yaml packages keys with dp.parse(depPath).name and uses it without validation in deps/graph-builder/src/lockfileToDepGraph.ts and pnpm11/deps/graph-builder/src/lockfileToDepGraph.ts. The name reaches path.join(modules, pkgName), storeController.importPackage, and pnpm11/lockfile/to-pnp/src/index.ts, allowing package contents to be written outside node_modules when a user runs pnpm install. When dangerouslyAllowAllBuilds or a matching allowBuilds entry permits lifecycle scripts, the escaped package can execute code with the user's privileges. This issue is fixed in versions 10.34.5 and 11.11.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-82392?

4 open source packages ship an affected version, including pnpm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pnpm` | npm | All versions | 10.34.5 |
| `pnpm` | npm | All versions | 10.34.5 |
| `pnpm` | npm | From 11.0.0 | 11.11.0 |
| `pnpm` | npm | From 11.0.0 | 11.11.0 |

## How do I fix CVE-2026-82392?

Upgrade pnpm to a fixed version for your release line: 10.34.5 or 11.11.0.

## Is CVE-2026-82392 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82392 and fix it if it is affected.

What it is: CVE-2026-82392 is a high-severity path traversal vulnerability in pnpm, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82392 in the wild and no public exploit code.

Affected packages and fixed versions:
- pnpm (npm): affected all versions; fixed in 10.34.5
- pnpm (npm): affected all versions; fixed in 10.34.5
- pnpm (npm): affected from 11.0.0; fixed in 11.11.0
- pnpm (npm): affected from 11.0.0; fixed in 11.11.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-2026-82392/ (Markdown: https://insights.sbomify.com/CVE-2026-82392/index.md)
```

## Sources

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

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