CVE-2022-26183 json
Untrusted Search Path in PNPM
published 2022-03-21 4 y ago modified 2026-06-17 4 mo ago also GHSA-9m87-6fj3-c5xh , EUVD-2022-1397
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm pnpm 6.15.1
- pnpm pnpm 6.15.1
Exploit prediction
1.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- sonarsource.com https://www.sonarsource.com/blog/securing-developer-tools-package-managers/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | pnpm | <6.15.1 |
6.15.1 |
Classification
- Weakness
-
- CWE-426 Untrusted Search Path
References
-
github.com
/pnpm/pnpm/commit/04b7f60861ddee8331e50d70e193d1e701abeefb
web, patch
-
sonarsource.com
/blog/securing-developer-tools-package-managers/
exploit, third-party-advisory
-
github.com
/pnpm/pnpm/releases/tag/v6.15.1
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2022-26183
advisory
-
github.com
/pnpm/pnpm
package
-
sonarsource.com
/blog/securing-developer-tools-package-managers
web
Sources
- CVE List CVE-2022-26183
- GitHub Advisory GHSA-9m87-6fj3-c5xh
- NVD CVE-2022-26183
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.