Nx: Zip-Slip in the self-hosted remote cache

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-71476: 0.86% estimated exploitation activity in the next 30 days; percentile 58.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Affected Packages [!IMPORTANT] 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 (NXSELFHOSTEDREMOTECACHESERVER, @nx/s3-cache, etc.) are affected. Two self-hosted cache surfaces are affected: 1. The built-in HTTP remote cache (NXSELFHOSTEDREMOTECACHESERVER, in nx) — fixed in the patched release. 2. The self-hosted cache packages — @nx/s3-cache,…

Published by the source

6 Aug 2026, 20:10 UTC

Last modified by the source

6 Aug 2026, 20:10 UTC

Source last checked

26 Oct 2026, 13:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vp3h-ghgh-jr7g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71476

Advisory: Nx: Zip-Slip in the self-hosted remote cache
IDs: CVE-2026-71476, GHSA-vp3h-ghgh-jr7g
Record: https://patchnext.com/advisories/cve-2026-71476 (revision 1, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: nx 23.0.2, 22.7.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nx/azure-cache: affected <= 5.0.7
- npm @nx/shared-fs-cache: affected <= 5.0.7
- npm @nx/powerpack-azure-cache: affected <= 5.0.7
- npm @nx/powerpack-gcs-cache: affected <= 5.0.7
- npm nx: affected >= 20.8.0, < 22.7.7; >= 23.0.0, < 23.0.2; fixed in 22.7.7, 23.0.2
- npm @nx/gcs-cache: affected <= 5.0.7
- npm @nx/powerpack-s3-cache: affected <= 5.0.7
- npm @nx/powerpack-shared-fs-cache: affected <= 5.0.7
- npm @nx/s3-cache: affected <= 5.0.7

## Suggested inspection (read-only)
- `npm ls @nx/azure-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nx/shared-fs-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nx/powerpack-azure-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nx/powerpack-gcs-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls nx --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nx/gcs-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nx/powerpack-s3-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nx/powerpack-shared-fs-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nx/s3-cache --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @nx/azure-cache, @nx/shared-fs-cache, @nx/powerpack-azure-cache, @nx/powerpack-gcs-cache, nx, @nx/gcs-cache, @nx/powerpack-s3-cache, @nx/powerpack-shared-fs-cache, @nx/s3-cache.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vp3h-ghgh-jr7g (GitHub-reviewed advisory GHSA-vp3h-ghgh-jr7g lists affected ranges: npm nx >=20.8.0 =23.0.0 =0 =0 =0 =0 =0 =0 =0 =0 <=5.0.7)

Commands are suggestions: review each one before running it.