Vulnerabilities in pkg:npm/@nx/powerpack-azure-cache

PACKAGE
Advisory Identifier: GHSA-vp3h-ghgh-jr7g
Advisory Summary

CVE-2026-71476 is a HIGH zip-slip vulnerability (CWE-59: Improper Link Resolution Before File Access ('Link Following')) affecting Nx libraries in the npm ecosystem. The issue involves zip-slip in the self-hosted remote cache. Remediation is available by upgrading affected packages to version 22.7.7, 23.0.2.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@nx/powerpack-azure-cache

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@nx/powerpack-azure-cache. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-vp3h-ghgh-jr7g CVE-2026-71476 HIGH Nx: Zip-Slip in the self-hosted remote cache

CVE-2026-71476 at a Glance

CVE Identifier CVE-2026-71476
GHSA Identifier GHSA-vp3h-ghgh-jr7g
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-59: Improper Link Resolution Before File Access ('Link Following')
Affected Product Nx
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-71476

To remediate this vulnerability, upgrade all affected Nx dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nx fixed: 22.7.7
npm install nx@22.7.7
@nx/s3-cache fixed: Latest secure release
npm install @nx/s3-cache@Latest secure release
@nx/gcs-cache fixed: Latest secure release
npm install @nx/gcs-cache@Latest secure release
@nx/azure-cache fixed: Latest secure release
npm install @nx/azure-cache@Latest secure release
@nx/shared-fs-cache fixed: Latest secure release
npm install @nx/shared-fs-cache@Latest secure release
@nx/powerpack-s3-cache fixed: Latest secure release
npm install @nx/powerpack-s3-cache@Latest secure release
@nx/powerpack-gcs-cache fixed: Latest secure release
npm install @nx/powerpack-gcs-cache@Latest secure release
@nx/powerpack-azure-cache fixed: Latest secure release
npm install @nx/powerpack-azure-cache@Latest secure release
@nx/powerpack-shared-fs-cache fixed: Latest secure release
npm install @nx/powerpack-shared-fs-cache@Latest secure release
nx fixed: 23.0.2
npm install nx@23.0.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls nx

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-71476, inspect your project dependencies using npm:

npm ls nx

Analyze the terminal output to locate any version of Nx in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 22.7.7), your application is affected.

Note: The npm ls nx command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following'), where the product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. In Nx, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 (`NX_SELF_HOSTED_REMOTE_CACHE_SERVER`, `@nx/s3-cache`, etc.) are affected. Two self-hosted cache surfaces are affected: 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). The shared step that copies cached outputs into the workspace was also part of the exposure and is hardened in the patched `nx` release. ## Remediation **Upgrade to Nx `22.7.7` or `23.0.2` (or later).** The patched extractor is a drop-in — no configuration change is required. ### If you use the S3, GCS, Azure, or shared-filesystem cache packages `@nx/s3-cache`, `@nx/gcs-cache`, `@nx/azure-cache`, and `@nx/shared-fs-cache` (and their `@nx/powerpack-*` predecessors) are separately versioned packages and are **already deprecated** (see CVE-2025-36852). Upgrading `nx` hardens the shared restore step, but it does not fully secure these packages. The remediation for them is to **migrate off** — to Nx Cloud or the self-hosted OpenAPI/HTTP remote cache — per the deprecation guidance: https://nx.dev/docs/reference/deprecated/self-hosted-cache-packages ## Details When Nx retrieves an artifact from the self-hosted HTTP remote cache, it downloads a gzipped tar archive and extracts it. The extractor joined each untrusted tar entry name directly onto the output directory and unpacked it with `tar`'s **unguarded** `Entry::unpack()`, which performs no containment check: ```rust // vulnerable let path_on_disk = output_dir.join(entry_path); // entry_path is attacker-controlled fs::create_dir_all(path_on_disk.parent()…)?; entry.unpack(&path_on_disk)?; ``` In addition, restore now copies **only** the declared task outputs (never the whole cache directory), confined to the workspace root; parent directories are realized as real directories so a write can never traverse a symlink; declared outputs that resolve outside the workspace are rejected; and the malformed-input cases return errors instead of panicking. ## References - Fix: https://github.com/nrwl/nx/pull/36116 (merged) - TLS-verification warning follow-up: https://github.com/nrwl/nx/pull/36132 (merged) - Vulnerable extractor introduced in Nx 20.8.0: https://github.com/nrwl/nx/pull/30593 ## Credits - **Lidor B.**, Novee Security — Reporter - **Assaf Levkovich**, Novee Security — Reporter

CVE-2026-71476 Affected Nx Versions

10 component(s)
Fixed Versions:
22.7.723.0.2
Product / Package Ecosystem Affected Versions Fixed Version
nx
npm
≥ 20.8.0
< 22.7.7
22.7.7
@nx/s3-cache
npm
≤ 5.0.7
@nx/gcs-cache
npm
≤ 5.0.7
@nx/azure-cache
npm
≤ 5.0.7
@nx/shared-fs-cache
npm
≤ 5.0.7
@nx/powerpack-s3-cache
npm
≤ 5.0.7
@nx/powerpack-gcs-cache
npm
≤ 5.0.7
@nx/powerpack-azure-cache
npm
≤ 5.0.7
@nx/powerpack-shared-fs-cache
npm
≤ 5.0.7
nx
npm
≥ 23.0.0
< 23.0.2
23.0.2

References

Frequently Asked Questions

What is CVE-2026-71476?
CVE-2026-71476 is a security vulnerability in Nx involving Zip-Slip in the self-hosted remote cache under CWE-59: Improper Link Resolution Before File Access ('Link Following').
Which Nx versions are affected?
Affected versions include releases prior to 22.7.7, 23.0.2 across affected packages: nx, @nx/s3-cache, @nx/gcs-cache, @nx/azure-cache, @nx/shared-fs-cache, @nx/powerpack-s3-cache, @nx/powerpack-gcs-cache, @nx/powerpack-azure-cache, @nx/powerpack-shared-fs-cache.
What version fixes CVE-2026-71476?
Upgrading to 22.7.7, 23.0.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nx affected?
Yes, nx is affected in releases prior to 22.7.7, 23.0.2. Upgrade your dependency to 22.7.7, 23.0.2 or later.
Is @nx/s3-cache affected?
Yes, @nx/s3-cache is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with CVE-2026-71476?
CVE-2026-71476 is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following') (The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.).
How can I check npm dependencies for CVE-2026-71476?
Run the dependency tree command: 'npm ls nx'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vp3h-ghgh-jr7g",
  "modified" : "2026-08-06T20:10:03Z",
  "published" : "2026-08-06T20:10:03Z",
  "aliases" : [ "CVE-2026-71476" ],
  "summary" : "Nx: Zip-Slip in the self-hosted remote cache",
  "details" : "## Summary\n\nThe 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.\n\n## Affected Packages\n\n> [!IMPORTANT]\n> **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.\n\nTwo self-hosted cache surfaces are affected:\n\n1. **The built-in HTTP remote cache** (`NX_SELF_HOSTED_REMOTE_CACHE_SERVER`, in `nx`) — **fixed** in the patched release.\n2. **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).\n\nThe shared step that copies cached outputs into the workspace was also part of the exposure and is hardened in the patched `nx` release.\n\n## Remediation\n\n**Upgrade to Nx `22.7.7` or `23.0.2` (or later).** The patched extractor is a drop-in — no configuration change is required.\n\n### If you use the S3, GCS, Azure, or shared-filesystem cache packages\n\n`@nx/s3-cache`, `@nx/gcs-cache`, `@nx/azure-cache`, and `@nx/shared-fs-cache` (and their `@nx/powerpack-*` predecessors) are separately versioned packages and are **already deprecated** (see CVE-2025-36852). Upgrading `nx` hardens the shared restore step, but it does not fully secure these packages. The remediation for them is to **migrate off** — to Nx Cloud or the self-hosted OpenAPI/HTTP remote cache — per the deprecation guidance: https://nx.dev/docs/reference/deprecated/self-hosted-cache-packages\n\n## Details\n\nWhen Nx retrieves an artifact from the self-hosted HTTP remote cache, it downloads a gzipped tar archive and extracts it. The extractor joined each untrusted tar entry name directly onto the output directory and unpacked it with `tar`'s **unguarded** `Entry::unpack()`, which performs no containment check:\n\n```rust\n// vulnerable\nlet path_on_disk = output_dir.join(entry_path); // entry_path is attacker-controlled\nfs::create_dir_all(path_on_disk.parent()…)?;\nentry.unpack(&path_on_disk)?;\n```\n\nIn addition, restore now copies **only** the declared task outputs (never the whole cache directory), confined to the workspace root; parent directories are realized as real directories so a write can never traverse a symlink; declared outputs that resolve outside the workspace are rejected; and the malformed-input cases return errors instead of panicking.\n\n## References\n\n- Fix: https://github.com/nrwl/nx/pull/36116 (merged)\n- TLS-verification warning follow-up: https://github.com/nrwl/nx/pull/36132 (merged)\n- Vulnerable extractor introduced in Nx 20.8.0: https://github.com/nrwl/nx/pull/30593\n\n## Credits\n\n- **Lidor B.**, Novee Security — Reporter\n- **Assaf Levkovich**, Novee Security — Reporter",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.8.0"
      }, {
        "fixed" : "22.7.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/s3-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/gcs-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/azure-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/shared-fs-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/powerpack-s3-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/powerpack-gcs-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/powerpack-azure-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nx/powerpack-shared-fs-cache"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "23.0.0"
      }, {
        "fixed" : "23.0.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nrwl/nx/security/advisories/GHSA-vp3h-ghgh-jr7g"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nrwl/nx/pull/36116"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nrwl/nx/commit/2b20c2da39d263c32ae05767577589481a309fee"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nrwl/nx/commit/a82807621e4176e37909d2c1afede661b45cc30"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nrwl/nx/commit/ad296578fe980a4aad66f8af0add21f6ddf907d9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nrwl/nx"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-59" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-06T20:10:03Z",
    "nvd_published_at" : null
  }
}