node-tar is a full-featured Tar for Node.js. When using default options in versions 7.5.7 and below, an attacker-controlled archive can create a hardlink inside the extraction directory that points to a file outside the extraction root, enabling arbitrary file read and write as the extracting user. Severity is high because the primitive bypasses path protections and turns archive extraction into a direct filesystem access primitive. This issue has been fixed in version 7.5.8.
CVE-2026-26960
HIGHNVD 7.17.1Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1(low)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
February 20, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/isaacs/node-tar/commit/2cb1120bcefe28d7ecc719b41441ade59c52e384
- security-advisories@githubhttps://github.com/isaacs/node-tar/commit/d18e4e1f846f4ddddc153b0f536a19c050e7499f
- security-advisories@githubhttps://github.com/isaacs/node-tar/security/advisories/GHSA-83g3-92jg-28cx
Vendor Advisories for CVE-2026-26960(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:6428Red Hat Product SecurityHigh
Red Hat Security Advisory: Network Observability 1.11.1 for OpenShift
- RHSA-2026:6192Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.27.0 Release.
- RHSA-2026:5447Red Hat Product SecurityHigh
Red Hat Security Advisory: RHTAS 1.3.3 - Red Hat Trusted Artifact Signer Release
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | network-observability/network-observability-console-plugin-rhel9:1774431617 | 2026-04-02 | redhat |
| redhat | devspaces/dashboard-rhel9:1774476526 | 2026-03-30 | redhat |
| redhat | rhtas/rekor-search-ui-rhel9:1773308315 | 2026-03-23 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tar | — | 7.5.8 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 12:55 UTCEG score recompute
- 2026-07-27 12:55 UTCVendor advisory
- 2026-07-27 12:50 UTCOSV refresh
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p90HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-26960?
CVE-2026-26960 is a high vulnerability published on February 20, 2026. node-tar is a full-featured Tar for Node.js. When using default options in versions 7.5.7 and below, an attacker-controlled archive can create a hardlink inside the extraction directory that points to a file outside the extraction root, enabling arbitrary file read and write as the extracting user.…
When was CVE-2026-26960 disclosed?
CVE-2026-26960 was first published in the National Vulnerability Database on February 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26960 actively exploited?
CVE-2026-26960 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.0% of all scored CVEs.
What is the CVSS score of CVE-2026-26960?
CVE-2026-26960 has a CVSS v3 base score of 7.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-26960?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26960, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26960
Is Your Infrastructure Affected by CVE-2026-26960?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.