CVE-2026-59873

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). 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: 0.6%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.19, node-tar does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio in extraction and parsing paths such as src/extract.ts, allowing a small crafted gzip bomb to exhaust disk space and CPU. This issue is fixed in version 7.5.19.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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.6%
EPSS %ILE
49th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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_commit, github.
githubMentions a patch (unverified)🟡 PoC Available

Decompression/parse DoS via unlimited input · Advisory · isaacs/node-tar · GitHub

https://github.com/isaacs/node-tar/security/advisories/GHSA-23hp-3jrh-7fpw
github_commit

commit 2812e9338665 (isaacs/node-tar)

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

https://github.com/isaacs/node-tar/commit/2812e9338665659b183aa7226518c307044957d3

Patch Availability(27)

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
redhatansible-automation-platform/bootc-automation-portal-rhel9:17860065732026-08-06redhat
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
redhatnodejs24-1:24.18.0-3.el10_22026-07-29redhat
redhatnodejs22-1:22.23.1-4.el10_22026-07-29redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847215812026-07-28redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847137412026-07-28redhat
redhatnodejs:22-8100020260724100938.6d8804032026-07-28redhat
redhatnodejs:24-8100020260724132848.6d8804032026-07-28redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847246992026-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.19: fixed in 7.5.19
—

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 7× in last 7d / 41× 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 214 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-59873?
CVE-2026-59873 is a high vulnerability published on July 8, 2026. node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.19, node-tar does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio in extraction and parsing paths such as src/extract.ts, allowing a small crafted gzip bomb to exhaust disk space…
When was CVE-2026-59873 disclosed?
CVE-2026-59873 was first published 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-59873 actively exploited?
CVE-2026-59873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59873?
CVE-2026-59873 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59873?
A fix for CVE-2026-59873 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59873 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-59873

Explore →

Is Your Infrastructure Affected by CVE-2026-59873?

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