# CVE-2022-26183: Untrusted Search Path in PNPM

> Attackers can execute arbitrary code by placing malicious files in a directory where PNPM is run on Windows.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9m87-6fj3-c5xh

## What is CVE-2022-26183?

CVE-2022-26183 is a high-severity path traversal vulnerability in n/a, published on 21 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PNPM v6.15.1 and below was discovered to contain an untrusted search path which causes the application to behave in unexpected ways when users execute PNPM commands in a directory containing malicious content. This vulnerability occurs when the application is ran on Windows OS.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2022-26183?

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


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

Products: Pnpm Pnpm.

## How do I fix CVE-2022-26183?

Upgrade pnpm to 6.15.1 or later.

## Is CVE-2022-26183 being exploited?

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

## Other vulnerabilities in n/a

- [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-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)
- [CVE-2025-69262](https://insights.sbomify.com/CVE-2025-69262/): pnpm vulnerable to Command Injection via environment variable substitution (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26183 and fix it if it is affected.

What it is: CVE-2022-26183 is a high-severity path traversal vulnerability in n/a, published on 21 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26183 in the wild and no public exploit code.

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

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

## Sources

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

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