<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 09:44:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-69264 — pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-69264</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pnpm, Red Hat JBoss Enterprise Application Platform 8, Red Hat JBoss Enterprise Application Platform Expansion Pack&lt;/p&gt;
&lt;p&gt;pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during pnpm install, circumventing the v10 security feature &amp;#34;Dependency lifecycle scripts execution disabled by default&amp;#34;. While pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, git dependencies can still execute prepare, prepublish, and prepack scripts during the fetch phase, enabling remote code execution without user consent or approval. This issue is fixed in version 10.26.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pnpm, Red Hat JBoss Enterprise Application Platform 8, Red Hat JBoss Enterprise Application Platform Expansion Pack&lt;/p&gt;
&lt;p&gt;pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during pnpm install, circumventing the v10 security feature &amp;#34;Dependency lifecycle scripts execution disabled by default&amp;#34;. While pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, git dependencies can still execute prepare, prepublish, and prepack scripts during the fetch phase, enabling remote code execution without user consent or approval. This issue is fixed in version 10.26.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-69264</guid>
    </item>
    <item>
      <title>GHSA-379q-355j-w6rj — pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default"</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-379q-355j-w6rj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: pnpm&lt;/p&gt;
&lt;p&gt;# pnpm v10+ Git Dependency Script Execution Bypass&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A security bypass vulnerability in pnpm v10+ allows git-hosted dependencies to execute arbitrary code during `pnpm install`, circumventing the v10 security feature &amp;#34;Dependency lifecycle scripts execution disabled by default&amp;#34;. While pnpm v10 blocks `postinstall` scripts via the `onlyBuiltDependencies` mechanism, git dependencies can still execute `prepare`, `prepublish`, and `prepack` scripts during the fetch phase, enabling remote code execution without user consent or approval.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;pnpm v10 introduced a security feature to disable dependency lifecycle scripts by default ([PR #8897](https://github.com/pnpm/pnpm/pull/8897)). This is implemented by setting `onlyBuiltDependencies = []` when no build policy is configured:&lt;/p&gt;
&lt;p&gt;**File:** `pkg-manager/core/src/install/extendInstallOptions.ts` (lines 290-291)
```typescript
if (opts.neverBuiltDependencies == null &amp;amp;&amp;amp; opts.onlyBuiltDependencies == null &amp;amp;&amp;amp; opts.onlyBuiltDependenciesFile == null) {
  opts.onlyBuiltDependencies = []
}
```&lt;/p&gt;
&lt;p&gt;This creates an allowlist that blocks all packages from running scripts during the **BUILD phase** in `exec/build-modules/src/index.ts`.&lt;/p&gt;
&lt;p&gt;However, git-hosted dependencies are processed differently. During the **FETCH phase**, git packages are prepared using `preparePackage()`:&lt;/p&gt;
&lt;p&gt;**File:** `exec/prepare-package/src/index.ts` (lines 28-57)
```typescript
export async function preparePackage (opts: PreparePackageOptions, gitRootDir: stri…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: pnpm&lt;/p&gt;
&lt;p&gt;# pnpm v10+ Git Dependency Script Execution Bypass&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A security bypass vulnerability in pnpm v10+ allows git-hosted dependencies to execute arbitrary code during `pnpm install`, circumventing the v10 security feature &amp;#34;Dependency lifecycle scripts execution disabled by default&amp;#34;. While pnpm v10 blocks `postinstall` scripts via the `onlyBuiltDependencies` mechanism, git dependencies can still execute `prepare`, `prepublish`, and `prepack` scripts during the fetch phase, enabling remote code execution without user consent or approval.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;pnpm v10 introduced a security feature to disable dependency lifecycle scripts by default ([PR #8897](https://github.com/pnpm/pnpm/pull/8897)). This is implemented by setting `onlyBuiltDependencies = []` when no build policy is configured:&lt;/p&gt;
&lt;p&gt;**File:** `pkg-manager/core/src/install/extendInstallOptions.ts` (lines 290-291)
```typescript
if (opts.neverBuiltDependencies == null &amp;amp;&amp;amp; opts.onlyBuiltDependencies == null &amp;amp;&amp;amp; opts.onlyBuiltDependenciesFile == null) {
  opts.onlyBuiltDependencies = []
}
```&lt;/p&gt;
&lt;p&gt;This creates an allowlist that blocks all packages from running scripts during the **BUILD phase** in `exec/build-modules/src/index.ts`.&lt;/p&gt;
&lt;p&gt;However, git-hosted dependencies are processed differently. During the **FETCH phase**, git packages are prepared using `preparePackage()`:&lt;/p&gt;
&lt;p&gt;**File:** `exec/prepare-package/src/index.ts` (lines 28-57)
```typescript
export async function preparePackage (opts: PreparePackageOptions, gitRootDir: stri…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-379q-355j-w6rj</guid>
    </item>
  </channel>
</rss>
