LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24842: node-tar Vulnerable to Arbitrary File Creation/Overwrite via Hardlink Path Traversal

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. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path traversal protections and creates hardlinks to arbitrary files outside the extraction directory. Version 7.5.7 contains a fix for the issue.

HighCVSS 8.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Applications using vulnerable node-tar versions can be tricked by a malicious TAR archive into creating or overwriting files outside the intended extraction folder. Exploitation requires the archive to be extracted, but resulting file access crosses a security boundary and could expose sensitive information or alter files accessible to the application.

Executive priority

Prioritize remediation for internet-facing upload, package-processing, CI/CD, and automation systems that extract untrusted archives. Upgrade promptly because exploitation is low complexity once extraction occurs and can cross filesystem boundaries. Systems that never process untrusted TAR files are lower priority, but dependency inventory is still warranted.

Technical view

Before node-tar 7.5.7, validation and creation resolve hardlink paths differently. A crafted hardlink entry can therefore pass traversal checks while the extraction logic targets a file outside the destination directory. The published CVSS 3.1 score is 8.2, reflecting network-deliverable input, low complexity, required extraction interaction, changed scope, high confidentiality impact, and low integrity impact.

Likely exposure

Exposure is most likely where an application, build system, or service uses node-tar below 7.5.7 to extract attacker-supplied or otherwise untrusted TAR archives. Risk depends on the permissions of the extracting process and reachable files. Direct and transitive dependencies should both be examined.

Exploitation context

The supplied record does not identify this CVE as a CISA KEV and provides no evidence of active exploitation. An attacker must get a crafted archive extracted by a vulnerable application or user workflow. No conclusion about public exploit availability can be drawn from the supplied sources.

Researcher notes

CWE-22 and CWE-59 capture the traversal and link-following aspects. The key defect is a semantic mismatch between the hardlink security check and actual link creation. Assess effective process privileges, extraction entry points, archive trust boundaries, and reachable sensitive files. The supplied evidence does not establish active exploitation or affected products beyond node-tar and referenced Red Hat advisories.

Mitigation direction

  • Upgrade node-tar to version 7.5.7 or later.
  • Update lockfiles and rebuild deployments so the corrected dependency is actually installed.
  • Apply applicable Red Hat advisories when node-tar is supplied through affected Red Hat products.
  • Until updated, avoid extracting untrusted TAR archives with vulnerable components.
  • Limit the extracting process to only necessary filesystem permissions.

Validation and detection

  • Inventory direct and transitive node-tar versions across applications, build systems, and deployed artifacts.
  • Confirm package manifests and lockfiles resolve node-tar to 7.5.7 or later.
  • Verify running containers and production bundles contain the corrected version, not only source repositories.
  • Identify every workflow that extracts TAR archives from external or untrusted sources.
  • After remediation, confirm extraction cannot modify files outside its designated directory in an isolated test.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-59: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24842 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N2.84.7GitHub_M
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N2.84.7redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2026-24842Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPnode-tar: tar: node-tar: Arbitrary file creation via path traversal bypass in hardlink security check
other:Red Hat severity ratingcvssV3_1
  • 2026-01-28T01:01:16.886Z: Reported to Red Hat.
  • 2026-01-28T00:20:13.261Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
isaacsnode-tar< 7.5.7Listed
Weakness

CWE details

CWE-22CWE-59

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-59 · source CWE mapping

Improper Link Resolution Before File Access ('Link Following')

Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs