<?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://cve.radiocsirt.org</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>Thu, 08 Oct 2026 03:54:32 +0000</lastBuildDate>
    <item>
      <title>BREW-pnpm-CVE-2026-59195 — pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config</title>
      <link>https://cve.radiocsirt.org/vuln/brew-pnpm-cve-2026-59195</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: pnpm&lt;/p&gt;
&lt;p&gt;pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A malicious repository can commit a crafted pnpm-lock.yaml whose env-lockfile document contains a traversal-shaped config dependency name. During pnpm install, pnpm installs the config dependency and creates a symlink at a path derived from that name. This vulnerability is fixed in 10.34.4 and 11.8.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: pnpm&lt;/p&gt;
&lt;p&gt;pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A malicious repository can commit a crafted pnpm-lock.yaml whose env-lockfile document contains a traversal-shaped config dependency name. During pnpm install, pnpm installs the config dependency and creates a symlink at a path derived from that name. This vulnerability is fixed in 10.34.4 and 11.8.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-pnpm-cve-2026-59195</guid>
    </item>
    <item>
      <title>EUVD-2026-333667</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-333667</link>
      <description>EUVD-2026-333667</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-333667</guid>
    </item>
    <item>
      <title>fkie_cve-2026-59195</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59195</link>
      <description>&lt;p&gt;pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A malicious repository can commit a crafted pnpm-lock.yaml whose env-lockfile document contains a traversal-shaped config dependency name. During pnpm install, pnpm installs the config dependency and creates a symlink at a path derived from that name. This vulnerability is fixed in 10.34.4 and 11.8.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A malicious repository can commit a crafted pnpm-lock.yaml whose env-lockfile document contains a traversal-shaped config dependency name. During pnpm install, pnpm installs the config dependency and creates a symlink at a path derived from that name. This vulnerability is fixed in 10.34.4 and 11.8.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-59195</guid>
    </item>
    <item>
      <title>GHSA-qrv3-253h-g69c — pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qrv3-253h-g69c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: pnpm&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`pnpm` accepts package names from the env lockfile `configDependencies` section and uses those names directly when creating config dependency symlinks under `node_modules/.pnpm-config`.&lt;/p&gt;
&lt;p&gt;A malicious repository can commit a crafted `pnpm-lock.yaml` whose env-lockfile document contains a traversal-shaped config dependency name such as `../../PWNED_CFGDEP`. During `pnpm install`, pnpm installs the config dependency and creates a symlink at a path derived from that name.&lt;/p&gt;
&lt;p&gt;In local testing against pnpm `v11.5.1`, this caused pnpm to create a symlink outside the intended config dependency directory:&lt;/p&gt;
&lt;p&gt;```text
expected root: /tmp/pnpm-cfgdep-poc-sznwgunx/victim/node_modules/.pnpm-config
actual path:   /tmp/pnpm-cfgdep-poc-sznwgunx/victim/PWNED_CFGDEP
```&lt;/p&gt;
&lt;p&gt;This works with `--ignore-scripts`, so it does not rely on lifecycle script execution.&lt;/p&gt;
&lt;p&gt;## Vulnerable behavior&lt;/p&gt;
&lt;p&gt;The vulnerable behavior appears to be that `configDependencies` keys from the env lockfile are trusted as package names and used in filesystem paths without rejecting traversal components.&lt;/p&gt;
&lt;p&gt;The relevant pattern is:&lt;/p&gt;
&lt;p&gt;```ts
const configModulesDir = path.join(opts.rootDir, &amp;#39;node_modules/.pnpm-config&amp;#39;)&lt;/p&gt;
&lt;p&gt;for (const [pkgName, pkg] of Object.entries(normalizedDeps)) {
  const configDepPath = path.join(configModulesDir, pkgName)&lt;/p&gt;
&lt;p&gt;const pkgDirInGlobalVirtualStore = path.join(
    globalVirtualStoreDir,
    relPath,
    &amp;#39;node_modules&amp;#39;,
    pkgName
  )&lt;/p&gt;
&lt;p&gt;await symlinkDir(pkgDirInGlobalVirtualStore, configDepPath)
}
``…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: pnpm&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`pnpm` accepts package names from the env lockfile `configDependencies` section and uses those names directly when creating config dependency symlinks under `node_modules/.pnpm-config`.&lt;/p&gt;
&lt;p&gt;A malicious repository can commit a crafted `pnpm-lock.yaml` whose env-lockfile document contains a traversal-shaped config dependency name such as `../../PWNED_CFGDEP`. During `pnpm install`, pnpm installs the config dependency and creates a symlink at a path derived from that name.&lt;/p&gt;
&lt;p&gt;In local testing against pnpm `v11.5.1`, this caused pnpm to create a symlink outside the intended config dependency directory:&lt;/p&gt;
&lt;p&gt;```text
expected root: /tmp/pnpm-cfgdep-poc-sznwgunx/victim/node_modules/.pnpm-config
actual path:   /tmp/pnpm-cfgdep-poc-sznwgunx/victim/PWNED_CFGDEP
```&lt;/p&gt;
&lt;p&gt;This works with `--ignore-scripts`, so it does not rely on lifecycle script execution.&lt;/p&gt;
&lt;p&gt;## Vulnerable behavior&lt;/p&gt;
&lt;p&gt;The vulnerable behavior appears to be that `configDependencies` keys from the env lockfile are trusted as package names and used in filesystem paths without rejecting traversal components.&lt;/p&gt;
&lt;p&gt;The relevant pattern is:&lt;/p&gt;
&lt;p&gt;```ts
const configModulesDir = path.join(opts.rootDir, &amp;#39;node_modules/.pnpm-config&amp;#39;)&lt;/p&gt;
&lt;p&gt;for (const [pkgName, pkg] of Object.entries(normalizedDeps)) {
  const configDepPath = path.join(configModulesDir, pkgName)&lt;/p&gt;
&lt;p&gt;const pkgDirInGlobalVirtualStore = path.join(
    globalVirtualStoreDir,
    relPath,
    &amp;#39;node_modules&amp;#39;,
    pkgName
  )&lt;/p&gt;
&lt;p&gt;await symlinkDir(pkgDirInGlobalVirtualStore, configDepPath)
}
``…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qrv3-253h-g69c</guid>
    </item>
  </channel>
</rss>
