CVE-2026-59871

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. 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: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.18, node-tar coerces all-digit PAX path and linkpath values in src/pax.ts to JavaScript numbers, causing downstream path handling such as normalizeWindowsPath(entry.path).split('/') to throw an uncaught TypeError. This issue is fixed in version 7.5.18.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available

Process crash via PAX numeric path type confusion · Advisory · isaacs/node-tar · GitHub

https://github.com/isaacs/node-tar/security/advisories/GHSA-w8wr-v893-vjvp
github_commit

commit e02a4e9e013c (isaacs/node-tar)

Fix landed in isaacs/node-tar commit e02a4e9e013c — awaiting tagged release

https://github.com/isaacs/node-tar/commit/e02a4e9e013c4be95302e2eb2047a942b883c27b

Vendor Advisories for CVE-2026-59871(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-tar6.0.5+ds1+~cs11.3.9-1 ... 7.5.19+~4.0.1-2 (32 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-tar6.1.13+~cs7.0.5-1 ... 7.5.19+~4.0.1-2 (21 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-tar6.2.1+ds1+~cs6.1.13-1 ... 7.5.19+~4.0.1-2 (17 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-tar6.2.1+ds1+~cs6.1.13-1 ... 7.5.16+~4.0.1-2 (14 versions)7.5.19+~4.0.1-1—
npm(1)
PackageVulnerable rangeFixed inDependents
tar—7.5.18—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 55× 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.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 22:58 UTCEG score recompute
  3. 2026-08-24 10:04 UTCEG score recompute
  4. 2026-08-23 08:16 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 06:27 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 04:40 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 02:53 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 00:47 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 22:29 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 18:01 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 04:34 UTCEG score recompute
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 02:48 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 01:01 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 23:14 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 66 more
  1. 2026-08-11 21:27 UTCEG score recompute
  2. 2026-08-11 08:35 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-09 17:55 UTCEG score recompute
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-09 05:02 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-08 03:16 UTCEG score recompute
  9. 2026-08-07 01:30 UTCEG score recompute
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 23:43 UTCEG score recompute
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-04 21:53 UTCEG score recompute
  14. 2026-08-04 15:10 UTCEPSS rescore
  15. 2026-08-04 10:39 UTCEPSS rescore
  16. 2026-08-03 17:29 UTCEG score recompute
  17. 2026-08-03 10:36 UTCEPSS rescore
  18. 2026-08-02 02:46 UTCEG score recompute
  19. 2026-08-02 02:27 UTCEPSS rescore
  20. 2026-08-01 13:53 UTCEG score recompute
  21. 2026-08-01 04:16 UTCEPSS rescore
  22. 2026-07-30 23:07 UTCEG score recompute
  23. 2026-07-30 16:28 UTCEPSS rescore
  24. 2026-07-30 10:11 UTCEG score recompute
  25. 2026-07-30 01:30 UTCEPSS rescore
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-28 17:29 UTCEG score recompute
  28. 2026-07-28 15:37 UTCEPSS rescore
  29. 2026-07-27 15:39 UTCEG score recompute
  30. 2026-07-27 14:14 UTCEPSS rescore
  31. 2026-07-27 01:23 UTCEG score recompute
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 12:27 UTCEG score recompute
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-25 14:18 UTCEPSS rescore
  37. 2026-07-24 14:18 UTCEPSS rescore
  38. 2026-07-24 14:18 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 14:18 UTCEPSS rescore
  41. 2026-07-23 03:21 UTCEG score recompute
  42. 2026-07-22 14:08 UTCEPSS rescore
  43. 2026-07-22 14:08 UTCEPSS rescore
  44. 2026-07-21 15:25 UTCEPSS rescore
  45. 2026-07-21 15:25 UTCEPSS rescore
  46. 2026-07-20 17:08 UTCEPSS rescore
  47. 2026-07-19 14:31 UTCEPSS rescore
  48. 2026-07-19 02:29 UTCEPSS rescore
  49. 2026-07-18 10:04 UTCEPSS rescore
  50. 2026-07-16 17:03 UTCEPSS rescore
  51. 2026-07-15 16:57 UTCEPSS rescore
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 02:00 UTCEPSS rescore
  54. 2026-07-15 02:00 UTCEPSS rescore
  55. 2026-07-13 22:31 UTCEPSS rescore
  56. 2026-07-13 06:13 UTCEPSS rescore
  57. 2026-07-13 06:13 UTCEPSS rescore
  58. 2026-07-12 05:46 UTCEPSS rescore
  59. 2026-07-11 17:11 UTCEG score recompute▲ 2.20
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-10 20:19 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  63. 2026-07-09 19:10 UTCEPSS rescore
  64. 2026-07-09 19:10 UTCEPSS rescore
  65. 2026-07-08 15:46 UTCEG score recompute
  66. 2026-07-08 15:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59871?
CVE-2026-59871 is a high vulnerability published on July 8, 2026. node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.18, node-tar coerces all-digit PAX path and linkpath values in src/pax.ts to JavaScript numbers, causing downstream path handling such as normalizeWindowsPath(entry.path).split('/') to throw an uncaught TypeError. This issue…
When was CVE-2026-59871 disclosed?
CVE-2026-59871 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59871 actively exploited?
CVE-2026-59871 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.9% of all scored CVEs.
What is the CVSS score of CVE-2026-59871?
CVE-2026-59871 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59871?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59871, 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-59871

Explore →

Is Your Infrastructure Affected by CVE-2026-59871?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs