node-tar is a full-featured Tar for Node.js. Prior to version 7.5.11, tar (npm) can be tricked into creating a symlink that points outside the extraction directory by using a drive-relative symlink target such as C:../../../target.txt, which enables file overwrite outside cwd during normal tar.x() extraction. This vulnerability is fixed in 7.5.11.
CVE-2026-31802
HIGHNVD 5.58.2Trending — 4 sources updated this weekElevated
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.2 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
8.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0
A fix is available — apply it.
- CVSS v3
- 5.5
- EG Score
- 8.2(low)
- EG Risk
- 53(Track)EG Risk 53/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 computedSeverity82% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
March 9, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/isaacs/node-tar/commit/f48b5fa3b7985ddab96dc0f2125a4ffc9911b6ad
- security-advisories@githubhttps://github.com/isaacs/node-tar/security/advisories/GHSA-9ppj-qmqm-q256
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/isaacs/node-tar/security/advisories/GHSA-9ppj-qmqm-q256
Vendor Advisories for CVE-2026-31802(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | devspaces/dashboard-rhel9:1779341289 | 2026-05-28 | 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.11 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 12:54 UTCEG score recompute
- 2026-07-27 12:54 UTCVendor advisory
- 2026-07-27 12:50 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-31802?
CVE-2026-31802 is a high vulnerability published on March 9, 2026. node-tar is a full-featured Tar for Node.js. Prior to version 7.5.11, tar (npm) can be tricked into creating a symlink that points outside the extraction directory by using a drive-relative symlink target such as C:../../../target.txt, which enables file overwrite outside cwd during normal tar.x()…
When was CVE-2026-31802 disclosed?
CVE-2026-31802 was first published in the National Vulnerability Database on March 9, 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-31802 actively exploited?
CVE-2026-31802 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 83.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31802?
CVE-2026-31802 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-31802?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31802, 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-31802
Is Your Infrastructure Affected by CVE-2026-31802?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.