<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T14:32:56.101833+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-71476</id>
    <title>CVE-2026-71476 — Nx: Zip-Slip in the self-hosted remote cache</title>
    <updated>2026-09-30T14:32:56.105927+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> nrwl nx</p>
<p>Nx is a monorepo solution for TypeScript and polyglot codebases. From version 20.8.0 until 22.7.7 and 23.0.2, the Nx self-hosted HTTP remote cache extracts downloaded cache artifacts without constraining where files are written. A malicious or on-path (MITM) remote cache server can return a crafted tar archive whose entries escape the cache directory and write to arbitrary locations on the machine running Nx, which can be escalated to remote code execution. Nx's default local cache and Nx Cloud are not affected; only workspaces configured to use a self-hosted remote cache are affected. This issue is fixed in versions 22.7.7 and 23.0.2.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-71476"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-vp3h-ghgh-jr7g</id>
    <title>GHSA-vp3h-ghgh-jr7g — Nx: Zip-Slip in the self-hosted remote cache</title>
    <updated>2026-09-30T14:32:56.106027+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nx, npm: @nx/s3-cache, npm: @nx/gcs-cache, npm: @nx/azure-cache, npm: @nx/shared-fs-cache, npm: @nx/powerpack-s3-cache, npm: @nx/powerpack-gcs-cache, npm: @nx/powerpack-azure-cache, npm: @nx/powerpack-shared-fs-cache</p>
<p>## Summary</p>
<p>The Nx **self-hosted HTTP remote cache** extracts downloaded cache artifacts without constraining where files are written. A malicious — or on-path (MITM) — remote cache server can return a crafted tar archive whose entries escape the cache directory and write to arbitrary locations on the machine running Nx. This arbitrary file write can be escalated to remote code execution. The directly exploitable issue is the self-hosted HTTP remote cache.</p>
<p>## Affected Packages</p>
<p>&gt; [!IMPORTANT]
&gt; **Nx's default local cache and Nx Cloud are NOT affected.** The default local cache and Nx Cloud use separate cache retrieval and extraction mechanisms that does not have this vulnerability. Only workspaces that use a self-hosted remote cache (`NX_SELF_HOSTED_REMOTE_CACHE_SERVER`, `@nx/s3-cache`, etc.) are affected.</p>
<p>Two self-hosted cache surfaces are affected:</p>
<p>1. **The built-in HTTP remote cache** (`NX_SELF_HOSTED_REMOTE_CACHE_SERVER`, in `nx`) — **fixed** in the patched release.
2. **The self-hosted cache packages** — `@nx/s3-cache`, `@nx/gcs-cache`, `@nx/azure-cache`, `@nx/shared-fs-cache` (and their `@nx/powerpack-*` predecessors) — the same flaw in their own extractor. **Deprecated** (CVE-2025-36852) and not patched; migrate off (see Remediation).</p>
<p>The shared step that copies cached outputs into the workspace was also part of the exposure and is hardened in the patched `nx` release.</p>
<p>## Remediation</p>
<p>**Upgrade to Nx `22.7.7` or `23.0.2` (or later).** The patched extractor is a d…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-vp3h-ghgh-jr7g"/>
  </entry>
</feed>
