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 64% 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
Trending — 3 sources updated this weekElevated
7.5EG
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.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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)
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
0%
EPSS %ILE
36%
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(19)

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

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatnodejs22-1:22.23.1-3.el10_02026-08-11redhat
redhatnodejs:22-9060020260804140259.rhel92026-08-10redhat
redhatsatellite/iop-remediations-rhel9:17860080412026-08-06redhat
redhatopenshift-service-mesh/kiali-rhel9:17848063262026-08-03redhat
redhatopenshift-service-mesh/kiali-rhel9:17848139172026-08-03redhat
redhatnodejs:24-9080020260721131809.rhel92026-08-03redhat
redhatnodejs:22-9080020260721131741.rhel92026-08-03redhat
redhatopenshift-service-mesh/kiali-rhel9:17848064462026-08-03redhat
redhatopenshift-service-mesh/kiali-rhel9:17847954572026-08-03redhat
redhatnodejs24-1:24.18.0-3.el10_22026-07-29redhat
redhatnodejs22-1:22.23.1-4.el10_22026-07-29redhat
redhatdevspaces/dashboard-rhel9:17847371502026-07-29redhat
redhatnodejs:24-8100020260724132848.6d8804032026-07-28redhat
redhatnodejs:22-8100020260724100938.6d8804032026-07-28redhat
redhatansible-automation-platform/automation-portal:17846229512026-07-21redhat

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

(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 24× in last 7d / 108× 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.

Showing the most recent 100 of 151 total refreshes for this CVE.

  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-27 01:30 UTCEG score recompute
  3. 2026-08-27 01:30 UTCVendor advisory
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-26 08:25 UTCVendor advisory
  6. 2026-08-25 15:56 UTCEG score recompute
  7. 2026-08-25 15:56 UTCVendor advisory
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 02:21 UTCEG score recompute
  10. 2026-08-25 02:21 UTCVendor advisory
  11. 2026-08-24 13:10 UTCEG score recompute
  12. 2026-08-24 13:10 UTCVendor advisory
  13. 2026-08-24 00:01 UTCVendor advisory
  14. 2026-08-23 10:50 UTCEG score recompute
  15. 2026-08-23 10:50 UTCVendor advisory
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-22 21:40 UTCVendor advisory
  18. 2026-08-22 08:23 UTCEG score recompute
  19. 2026-08-22 08:23 UTCVendor advisory
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 19:13 UTCVendor advisory
  22. 2026-08-21 06:03 UTCEG score recompute
  23. 2026-08-21 06:03 UTCVendor advisory
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 16:53 UTCVendor advisory
Show 75 more
  1. 2026-08-20 03:39 UTCEG score recompute
  2. 2026-08-20 03:39 UTCVendor advisory
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 14:06 UTCVendor advisory
  5. 2026-08-19 00:54 UTCEG score recompute
  6. 2026-08-19 00:54 UTCVendor advisory
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-18 11:38 UTCVendor advisory
  9. 2026-08-17 22:29 UTCEG score recompute
  10. 2026-08-17 22:29 UTCVendor advisory
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 04:19 UTCVendor advisory
  13. 2026-08-16 15:09 UTCEG score recompute
  14. 2026-08-16 15:09 UTCVendor advisory
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-16 02:00 UTCVendor advisory
  18. 2026-08-15 12:50 UTCEG score recompute
  19. 2026-08-15 12:50 UTCVendor advisory
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 23:40 UTCVendor advisory
  22. 2026-08-14 10:30 UTCEG score recompute
  23. 2026-08-14 10:30 UTCVendor advisory
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 21:20 UTCVendor advisory
  26. 2026-08-13 08:08 UTCVendor advisory
  27. 2026-08-12 18:58 UTCEG score recompute
  28. 2026-08-12 18:58 UTCVendor advisory
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 05:48 UTCVendor advisory
  31. 2026-08-11 16:38 UTCEG score recompute
  32. 2026-08-11 16:38 UTCVendor advisory
  33. 2026-08-11 03:28 UTCEG score recompute
  34. 2026-08-11 03:28 UTCVendor advisory
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-10 14:19 UTCVendor advisory
  37. 2026-08-10 01:09 UTCEG score recompute
  38. 2026-08-10 01:09 UTCVendor advisory
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 12:00 UTCVendor advisory
  41. 2026-08-08 22:50 UTCEG score recompute
  42. 2026-08-08 22:50 UTCVendor advisory
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-08 09:40 UTCVendor advisory
  45. 2026-08-07 20:31 UTCEG score recompute
  46. 2026-08-07 20:31 UTCVendor advisory
  47. 2026-08-07 07:21 UTCVendor advisory
  48. 2026-08-06 18:11 UTCEG score recompute
  49. 2026-08-06 18:11 UTCVendor advisory
  50. 2026-08-06 13:47 UTCEPSS rescore
  51. 2026-08-06 05:02 UTCEG score recompute
  52. 2026-08-06 05:02 UTCVendor advisory
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-05 15:53 UTCVendor advisory
  55. 2026-08-04 23:22 UTCEG score recompute
  56. 2026-08-04 23:22 UTCVendor advisory
  57. 2026-08-04 15:10 UTCEPSS rescore
  58. 2026-08-04 10:39 UTCEPSS rescore
  59. 2026-08-04 10:12 UTCVendor advisory
  60. 2026-08-03 20:00 UTCEG score recompute
  61. 2026-08-03 20:00 UTCVendor advisory
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-03 06:50 UTCVendor advisory
  64. 2026-08-02 17:28 UTCVendor advisory
  65. 2026-08-02 04:19 UTCEG score recompute
  66. 2026-08-02 04:19 UTCVendor advisory
  67. 2026-08-02 02:27 UTCEPSS rescore
  68. 2026-08-01 15:09 UTCEG score recompute
  69. 2026-08-01 15:09 UTCVendor advisory
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-08-01 02:00 UTCVendor advisory
  72. 2026-07-31 12:48 UTCVendor advisory
  73. 2026-07-30 23:38 UTCEG score recompute
  74. 2026-07-30 23:38 UTCVendor advisory
  75. 2026-07-30 16:28 UTCEPSS rescore

Related CVEs(same vendor + 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 0% probability of exploitation in the next 30 days, which ranks it in the top 63.9% of all scored CVEs.
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