CVE-2026-59874

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

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(20)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17900139052026-09-30redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhattar2026-09-10redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatsatellite/iop-remediations-rhel9:17882305382026-09-03redhat
redhatdevspaces/openvsx-rhel9:17877591452026-09-01redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17871213872026-08-27redhat
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
redhatdevspaces/dashboard-rhel9:17847371502026-07-29redhat
redhatnodejs22-1:22.23.1-4.el10_22026-07-29redhat
redhatnodejs24-1:24.18.0-3.el10_22026-07-29redhat
redhatnodejs:22-8100020260724100938.6d8804032026-07-28redhat
redhatnodejs:24-8100020260724132848.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 rangeFix by version rangeDependents
node-tar6.0.5+ds1+~cs11.3.9-1 ... 7.5.19+~4.0.1-2 (32 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-tar6.1.13+~cs7.0.5-1 ... 7.5.22+~4.0.1-1 (22 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-tar6.2.1+ds1+~cs6.1.13-1 ... 7.5.22+~4.0.1-1 (18 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-tar6.2.1+ds1+~cs6.1.13-1 ... 7.5.16+~4.0.1-2 (14 versions)
  • every version up to 7.5.19+~4.0.1-1: fixed in 7.5.19+~4.0.1-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
tar—
  • every version up to 7.5.18: fixed in 7.5.18
—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 218 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59874?
CVE-2026-59874 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-59874 published?
The CVE record for CVE-2026-59874 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 10, 2026; the record at its source may have been updated since.
Is CVE-2026-59874 actively exploited?
CVE-2026-59874 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-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?
A fix for CVE-2026-59874 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59874 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs