CVE-2026-24842 - node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for h

CVE-2026-24842 + node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for h + High + 2026-01-28

One-sentence business risk

Filesystem escape can disclose secrets or overwrite trusted files, turning a dependency bug into host or account compromise.

Research notes

  • Root cause: node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic.
  • Affected versions: prior to 7.
  • Fixed / safe versions: Version 7.5.7 contains a fix for the issue…
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N.

Exact vulnerable code pattern

target = join(base_dir, user_path); read_or_write(target)

Fixed / mitigated code pattern

target = realpath(join(base_dir, user_path)); assert target is inside realpath(base_dir)

Dependency or runtime update:

npm ls node || true
npm install node@latest --save-exact
npm audit --omit=dev

Step-by-step integration guide

  1. Inventory node across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to Version 7.5.7 contains a fix for the issue. or apply the exact vendor patch referenced below.
  3. Replace the vulnerable path-traversal pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-24842-node-tar-a-tar-for-node-js-contains-a-vulnerabil
source: NVD bulk JSON feed
dependency_or_product: "node"
affected: "prior to 7"
fixed: "Version 7.5.7 contains a fix for the issue."
signals:
  - "path-traversal"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-24842 (node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for h) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to Version 7.5.7 contains a fix for the issue.. Replace the vulnerable path-traversal pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-24842, path-traversal, node, NVD bulk JSON feed.
  • Affected tech stack: javascript/npm.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References