CVE-2026-24842

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.6%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path traversal protections and creates hardlinks to arbitrary files outside the extraction directory. Version 7.5.7 contains a fix for the issue.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/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)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

January 28, 2026

Last Modified

September 7, 2026

Advisory Details (10)

Auto-updated Jun 30, 2026
Patch available. Sources: github_commit, github, redhat.
Red HatMentions a patch (unverified)

2433645 – (CVE-2026-24842) CVE-2026-24842 node-tar: tar: node-tar: Arbitrary file creation via path traversal bypass in hardlink security check

Affected: Red Hat Enterprise Linux 10

https://bugzilla.redhat.com/show_bug.cgi?id=2433645
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-24842
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6192
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:5447
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:33371
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:2900
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:18868
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:18480
GitHub advisoryMentions a patch (unverified)

Arbitrary File Read/Overwrite via Hardlink Path Traversal in node-tar · Advisory · isaacs/node-tar · GitHub

https://github.com/isaacs/node-tar/security/advisories/GHSA-34x7-hfp2-rc4v
GitHub commit

commit f4a7aa9bc3d7 (isaacs/node-tar)

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

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

Vendor Advisories for CVE-2026-24842(6)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap2026-06-30redhat
redhatlinux-sgx-0:2.26-7.el102026-05-19redhat
redhatlinux-sgx-0:2.26-7.el92026-05-19redhat
redhatdevspaces/dashboard-rhel9:17744765262026-03-30redhat
redhatrhtas/rekor-search-ui-rhel9:17733083152026-03-23redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17712276502026-02-18redhat

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

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-tar6.0.5+ds1+~cs11.3.9-1, 6.0.5+ds1+~cs11.3.9-1+deb11u1, 6.0.5+ds1+~cs11.3.9-1+deb11u2
  • every version up to 6.0.5+ds1+~cs11.3.9-1+deb11u3: fixed in 6.0.5+ds1+~cs11.3.9-1+deb11u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-tar6.2.1+ds1+~cs6.1.13-1 ... 6.2.1+~cs7.0.8-1 (10 versions)
  • every version up to 6.2.1+ds1+~cs6.1.13-10: fixed in 6.2.1+ds1+~cs6.1.13-10
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
tar—
  • every version up to 7.5.7: fixed in 7.5.7
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 30× 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 99 of 219 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-24842?
CVE-2026-24842 is a high-severity vulnerability; its CVE record was published on January 28, 2026. node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path…
When was the CVE record for CVE-2026-24842 published?
The CVE record for CVE-2026-24842 was published on January 28, 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 September 7, 2026; the record at its source may have been updated since.
Is CVE-2026-24842 actively exploited?
CVE-2026-24842 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24842?
CVE-2026-24842 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-24842?
A fix for CVE-2026-24842 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-24842 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-24842

Explore →

Is Your Infrastructure Affected by CVE-2026-24842?

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

Book a Demo →Browse All CVEs