https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 03:04:52 +0000 https://vulnerability.circl.lu/vuln/cve-2024-53866 <p><strong>Affected:</strong> pnpm</p> <p>The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don&#39;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. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace.</p> <p><strong>Affected:</strong> pnpm</p> <p>The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don&#39;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. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace.</p> https://vulnerability.circl.lu/vuln/cve-2024-53866 https://vulnerability.circl.lu/vuln/ghsa-vm32-9rqf-rh3r <p><strong>Affected:</strong> npm: pnpm</p> <p>### Summary</p> <p>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&#39;t revalidate the data (including on first lockfile generation)</p> <p>This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B</p> <p>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).</p> <p>Here, that expectation is broken</p> <p>### Details</p> <p>See PoC.</p> <p>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</p> <p>### PoC</p> <p>Postinstall code used in PoC is benign and can be inspected in &lt;https://www.npmjs.com/package/ponyhooves?activeTab=code&gt;, it&#39;s just a `console.log`</p> <p>1. Remove store and cache On mac: `rm -rf ~/Library/Caches/pnpm ~/Library/pnpm/store` This step is not required in general, but we&#39;ll be using a popular package for PoC that&#39;s likely cached 2. Create `A/package.json`: ```json { &#34;name&#34;: &#34;A&#34;, &#34;pnpm&#34;: { &#34;overrides&#34;: { &#34;rimraf&gt;glob&#34;: &#34;npm:ponyhooves@1&#34; } }, &#34;dependencies&#34;: { &#34;rimraf&#34;: &#34;6.0.1&#34; } } ``` Install it with `pnpm i --ignore-scripts` (the flag is not required, but the point of the demo is to show that it doesn&#39;t hel…</p> <p><strong>Affected:</strong> npm: pnpm</p> <p>### Summary</p> <p>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&#39;t revalidate the data (including on first lockfile generation)</p> <p>This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B</p> <p>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).</p> <p>Here, that expectation is broken</p> <p>### Details</p> <p>See PoC.</p> <p>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</p> <p>### PoC</p> <p>Postinstall code used in PoC is benign and can be inspected in &lt;https://www.npmjs.com/package/ponyhooves?activeTab=code&gt;, it&#39;s just a `console.log`</p> <p>1. Remove store and cache On mac: `rm -rf ~/Library/Caches/pnpm ~/Library/pnpm/store` This step is not required in general, but we&#39;ll be using a popular package for PoC that&#39;s likely cached 2. Create `A/package.json`: ```json { &#34;name&#34;: &#34;A&#34;, &#34;pnpm&#34;: { &#34;overrides&#34;: { &#34;rimraf&gt;glob&#34;: &#34;npm:ponyhooves@1&#34; } }, &#34;dependencies&#34;: { &#34;rimraf&#34;: &#34;6.0.1&#34; } } ``` Install it with `pnpm i --ignore-scripts` (the flag is not required, but the point of the demo is to show that it doesn&#39;t hel…</p> https://vulnerability.circl.lu/vuln/ghsa-vm32-9rqf-rh3r