CVE-2026-55699 json
pnpm: reserved bin name deletes PNPM_HOME during global remove
published 2026-06-25 4 mo ago modified 2026-06-29 4 mo ago also EUVD-2026-39485 , GHSA-4gxm-v5v7-fqc4
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
pnpm is a package manager. Prior to 10.34.2 and 11.5.3, Manifest bin object keys such as "", ".", and ".." passed pnpm's bin-name guard. When a malicious package was installed globally, later global remove, update, or add-replacement flows could re-derive those names from the installed manifest and pass path.join(globalBinDir, binName) to removeBin. For "." this targets the global bin directory; for ".." this targets its parent. This vulnerability is fixed in 10.34.2 and 11.5.3.
Patch / fix
- npm pnpm 10.34.2, 11.5.3
- pnpm pnpm 10.34.2, 11.5.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-55699 updated cvss 6.5
pnpm: pnpm: Denial of Service due to improper handling of malicious package manifest bin keys
-
Red Hat AMQ Broker 7 pnpm Red Hat Build of Keycloak pnpm Red Hat JBoss Enterprise Application Platform 8 pnpm Red Hat JBoss Enterprise Application Platform Expansion Pack pnpmaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/pnpm/pnpm/security/advisories/GHSA-4gxm-v5v7-fqc4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | pnpm | <10.34.2 >=11.0.0, <11.5.3 |
10.34.2 11.5.3 |
Affected products
- pnpm pnpm
Classification
References
-
github.com
/pnpm/pnpm/security/advisories/GHSA-4gxm-v5v7-fqc4
exploit, web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-55699
advisory
-
github.com
/pnpm/pnpm
package
Sources
- CVE List CVE-2026-55699
- GitHub Advisory GHSA-4gxm-v5v7-fqc4
- NVD CVE-2026-55699
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.