CVE-2026-59874

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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, tar.replace accepts a checksum-valid tar header with a negative base-256 encoded entry size, causing the archive scanner to make no progress while repeatedly parsing the same header. This issue is fixed in version 7.5.18.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
28.3%
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

Negative tar entry size causes infinite loop in archive replace · Advisory · isaacs/node-tar · GitHub

https://github.com/isaacs/node-tar/security/advisories/GHSA-8x88-c5mf-7j5w
github_commit

commit 9e78bf058b2c (isaacs/node-tar)

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

https://github.com/isaacs/node-tar/commit/9e78bf058b2c22dd4d52e00d8922d5c06fc2f7b5

Vendor Advisories for CVE-2026-59874(3)

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

Affected Packages

(1 across 1 ecosystem)
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 9× in last 7d / 25× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-13 22:31 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-10 20:26 UTCEG score recompute▼ 1.20
  21. 2026-07-10 20:19 UTCNVD updateCVSS v3 → 7.5
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-08 15:46 UTCEG score recompute
  25. 2026-07-08 15:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59874?
CVE-2026-59874 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, tar.replace accepts a checksum-valid tar header with a negative base-256 encoded entry size, causing the archive scanner to make no progress while repeatedly parsing the same header. This issue is fixed in version 7.5.18.
When was CVE-2026-59874 disclosed?
CVE-2026-59874 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-59874 actively exploited?
CVE-2026-59874 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59874?
CVE-2026-59874 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59874?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59874, 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-59874

Explore →

Is Your Infrastructure Affected by CVE-2026-59874?

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

Start Free Scan →Browse All CVEs