Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.8amended

pnpm no-script global cache poisoning via overrides / ignore-scripts evasion

CVE-2024-53866GHSA-vm32-9rqf-rh3r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pnpm 9.15.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm pnpm

    Affected
    < 9.15.0
    Fixed in
    9.15.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.8 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H · score source
EPSS
  • CVE-2024-53866: 0.98% estimated exploitation activity in the next 30 days; percentile 62.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary pnpm seems to mishandle overrides and global cache: 1. Overrides from one workspace leak into npm metadata saved in global cache 2. npm metadata from global cache affects other workspaces 3. installs by default don't revalidate the data (including on first lockfile generation) This can make workspace A (even running with ignore-scripts=true) posion global cache and execute scripts in workspace B Users generally expect ignore-scripts to be sufficient to prevent immediate code execution on install (e.g. when the tree is just repacked/bundled without executing it). Here, that expectation is broken Details See PoC. In it, overrides from a single run of A get leaked into e.g. ~/Library/Caches/pnpm/metadata/registry.npmjs.org/rimraf.json and persistently affect all other projects using the cache PoC Postinstall code used in PoC is benign and can be inspected in <https://www.npmjs.com/package/ponyhooves?activeTab=code, it's just a console.log 1. Remove store and cache On mac: rm -rf…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vm32-9rqf-rh3r

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-vm32-9rqf-rh3r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-53866

Advisory: pnpm no-script global cache poisoning via overrides / `ignore-scripts` evasion
IDs: CVE-2024-53866, GHSA-vm32-9rqf-rh3r
Record: https://patchnext.com/advisories/cve-2024-53866 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pnpm 9.15.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm pnpm: affected < 9.15.0; fixed in 9.15.0

## Suggested inspection (read-only)
- `npm ls pnpm --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pnpm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vm32-9rqf-rh3r (OSV record GHSA-vm32-9rqf-rh3r lists affected ranges: npm pnpm >=0 <9.15.0 (fixed))
- Verified: https://github.com/advisories/GHSA-vm32-9rqf-rh3r (GitHub-reviewed advisory GHSA-vm32-9rqf-rh3r lists affected ranges: npm pnpm >=0 <9.15.0)

Commands are suggestions: review each one before running it.

Loading voting…