Skip to main content
VulnerabilityPublished Updated

CVE-2026-55699: reserved bin name deletes PNPM_HOME during global remove

Affects pnpmSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 11.5.3 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade pnpm to 11.5.3.

Affected software

ProductAffectedFixed in
Homebrewpnpmpkg:brew/pnpmOther threatsAffected
  • >=4.0.2 <11.5.3
Fixed in
  • 11.5.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in pnpm versions 10.34.2 and 11.5.3. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated.

Description

A vulnerability in pnpm prior to versions 10.34.2 and 11.5.3 allows malicious packages using reserved bin names such as "." or ".." to cause deletion of the PNPM_HOME directory during global package removal. This occurs because these reserved names bypass pnpm's bin-name guard, leading to unintended directory removal. The issue is fixed in versions 10.34.2 and 11.5.3.

References

Community reviews

Loading reviews…