Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.86% for the current model date.
BlackTreeCVE Intelligencenrwl · nx
Official source article: GitHub GHSA-VP3H-GHGH-JR7G ↗. Check the applicable product and release in the original source.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npm@nx/azure-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npm@nx/gcs-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npm@nx/powerpack-azure-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npm@nx/powerpack-gcs-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npm@nx/powerpack-s3-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npm@nx/powerpack-shared-fs-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npm@nx/s3-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npm@nx/shared-fs-cache | <= 5.0.7 | Not stated | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npmnx | >= 20.8.0, < 22.7.7 | 22.7.7 | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npmnx | >= 23.0.0, < 23.0.2 | 23.0.2 | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly states that these products are not affected by this CVE.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Fix not verifiedNx 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.
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.
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.
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.
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 6 Aug 2026 · Last source change 8 Aug 2026, 02:33 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Core structured fields are present and their contributing authorities are shown above.