Security readout for executives and security teams
Plain-English summary
CVE-2026-24842 affects node-tar before 7.5.7. A malicious archive can bypass extraction safety checks and create or overwrite hardlinks outside the intended folder. Business risk is highest where systems accept or unpack external TAR files, such as uploads, build pipelines, package processing, or support tooling.
Executive priority
Treat as high priority for archive-processing services and build infrastructure. It is not confirmed as actively exploited, but the impact includes sensitive file exposure and limited integrity impact if malicious archives are processed.
Technical view
The issue is a path traversal and hardlink handling flaw. node-tar validates hardlink entries using path semantics that differ from the creation path, allowing crafted archives to escape the extraction directory. The CVSS 3.1 score is 8.2. The fixed version is 7.5.7.
Likely exposure
Exposure is likely in Node.js applications, CI systems, developer tools, or products that use node-tar below 7.5.7 and extract TAR archives from users, partners, repositories, or automated feeds.
Exploitation context
The sources indicate user interaction is required: a target must process a malicious TAR archive. CISA KEV is false in the bundle, and no provided source confirms active exploitation.
Researcher notes
Focus validation on hardlink entries, extraction root handling, and dependency reachability. The key nuance is mismatched path resolution between the security check and hardlink creation logic. Avoid assuming impact where TAR extraction is not reachable.
Mitigation direction
- Upgrade node-tar to 7.5.7 or later where directly managed.
- Apply relevant Red Hat errata for affected Red Hat-packaged products.
- Prioritize systems that extract externally supplied TAR archives.
- Isolate or suspend untrusted archive extraction until fixed.
- Check vendor guidance for transitive dependency remediation.
Validation and detection
- Inventory lockfiles and SBOMs for node-tar versions below 7.5.7.
- Identify applications and jobs that extract TAR files from untrusted sources.
- Confirm dependency resolution now uses node-tar 7.5.7 or later.
- Review Red Hat CVE, VEX, and errata applicability for deployed products.
- Verify no unsupported workaround replaced the vendor fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCWE-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 lookupFile 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 lookupCVE-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- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N2.84.7GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N2.84.7redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-01-28T01:01:16.886Z: Reported to Red Hat.
- 2026-01-28T00:20:13.261Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/isaacs/node-tar/security/advisories/GHSA-34x7-hfp2-rc4vCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/isaacs/node-tar/commit/f4a7aa9bc3d717c987fdf1480ff7a64e87ffdb46CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-24842CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2433645CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24842.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:33371CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:18480CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:18868CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:2900CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:6192CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:5447CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.
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.