LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23745: node-tar Vulnerable to Arbitrary File Overwrite and Symlink Poisoning via Insufficient Path Sanitization

node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3.

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

Security readout for executives and security teams

Plain-English summary

node-tar can be tricked into writing or pointing files outside the intended extraction folder when it processes a malicious archive. This matters for build, deployment, package, or upload workflows that extract tar files. The vulnerability is high severity and fixed in node-tar 7.5.3.

Executive priority

Treat as high priority for systems that ingest archives from users, vendors, or automated supply chains. Prioritize dependency updates and exposure review; urgency is lower for systems that never extract untrusted tar files.

Technical view

node-tar before 7.5.3 does not properly sanitize linkpath values for hardlink and symlink entries when preservePaths is false. A crafted tar archive can bypass extraction-root restrictions, causing arbitrary file overwrite through hardlinks or symlink poisoning through absolute symlink targets.

Likely exposure

Exposure is most likely where applications, CI/CD jobs, package tooling, or backend services use node-tar below 7.5.3 to extract untrusted or externally supplied tar archives.

Exploitation context

The source bundle does not show KEV listing or confirmed active exploitation. Exploitation requires a malicious archive to be extracted by a vulnerable node-tar consumer, with user interaction represented as archive processing.

Researcher notes

The key issue is linkpath sanitization for Link and SymbolicLink entries, not ordinary file paths. preservePaths false was expected to restrict extraction safely. Public sources name the fixed version but do not provide confirmed exploitation evidence.

Mitigation direction

  • Upgrade node-tar to 7.5.3 or later.
  • Audit direct and transitive dependencies for node-tar below 7.5.3.
  • Avoid extracting untrusted tar archives until patched.
  • Check Red Hat advisories for affected packaged products.
  • Review vendor guidance before applying product-specific fixes.

Validation and detection

  • Search package manifests and lockfiles for node-tar versions below 7.5.3.
  • Confirm deployed builds resolve node-tar to 7.5.3 or later.
  • Identify code paths that extract user-supplied or external tar archives.
  • Check CI/CD and packaging workflows for vulnerable node-tar use.
  • Verify relevant Red Hat errata status for managed platforms.
Prepared
Confidence
high
Sources
12

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
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-23745 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 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA: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
14Source 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 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N——GitHub_M
8.2CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H1.56redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

8.2High
CVSS 4.0 vector shape for CVE-2026-23745Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
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 overwrite and symlink poisoning via unsanitized linkpaths in archives
other:Red Hat severity ratingcvssV3_1
  • 2026-01-16T23:01:26.508Z: Reported to Red Hat.
  • 2026-01-16T22:00:08.769Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
isaacsnode-tar< 7.5.3Listed
Weakness

CWE details

CWE-22

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