CVE-2026-23950

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.3% (16th 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
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the path-reservations system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., ß and ss), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a PathReservations system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using NFD Unicode normalization (in which ß and ss are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which ß causes an inode collision with ss)). This enables an attacker to circumvent internal parallelization locks (PathReservations) using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates path-reservations.js to use a normalization form that matches the target filesystem's behavior (e.g., NFKD), followed by first toLocaleLowerCase('en') and then toLocaleUpperCase('en'). As a workaround, users who cannot upgrade promptly, and who are programmatically using node-tar to extract arbitrary tarball data should filter out all SymbolicLink entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.3%
EPSS %ILE
16th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (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 20, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Jul 15, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit 3b1abfae6500 (isaacs/node-tar)

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

https://github.com/isaacs/node-tar/commit/3b1abfae650056edfabcbe0a0df5954d390521e6
GitHub advisoryMentions a patch (unverified)

Race Condition in node-tar Path Reservations via Unicode Ligature Collisions on macOS APFS · Advisory · isaacs/node-tar · GitHub

https://github.com/isaacs/node-tar/security/advisories/GHSA-r6q2-hw4h-h46w

Vendor Advisories for CVE-2026-23950(5)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatlinux-sgx-0:2.26-7.el102026-05-19redhat
redhatlinux-sgx-0:2.26-7.el92026-05-19redhat
redhatdevspaces/udi-rhel9:17744519542026-03-30redhat
redhatrhtas/rekor-search-ui-rhel9:17707390562026-02-18redhat
redhatrhtas/rekor-search-ui-rhel9:17701074522026-02-05redhat

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+~cs7.0.8-1
  • every version up to 6.2.1+~cs7.0.8-1+deb13u1: fixed in 6.2.1+~cs7.0.8-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-tar6.2.1+ds1+~cs6.1.13-1 ... 6.2.1+~cs7.0.8-1 (7 versions)
  • every version up to 6.2.1+ds1+~cs6.1.13-7: fixed in 6.2.1+ds1+~cs6.1.13-7
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
tar—
  • every version up to 7.5.4: fixed in 7.5.4
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 12× 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 96 of 190 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 94 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.3% · 16th percentile
  2. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-12 16:20 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:47 UTCEG score recompute
  9. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  11. 2026-10-10 00:55 UTCOSV refresh
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  17. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  20. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  22. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  24. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  25. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.3% · 15th percentile
Show 71 more
  1. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-09-20 09:03 UTCOSV refresh
  3. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  8. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  12. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-09-01 12:25 UTCEG score recompute
  17. 2026-09-01 12:25 UTCVendor advisory
  18. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-08-24 13:32 UTCVendor advisory
  26. 2026-08-24 12:28 UTCEG score recompute
  27. 2026-08-24 12:28 UTCVendor advisory
  28. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-08-21 12:33 UTCEG score recompute
  30. 2026-08-21 12:33 UTCVendor advisory
  31. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-08-20 12:46 UTCEG score recompute
  33. 2026-08-20 12:46 UTCVendor advisory
  34. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  36. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  37. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  38. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  39. 2026-08-14 13:41 UTCEG score recompute
  40. 2026-08-14 13:41 UTCVendor advisory
  41. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  42. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  43. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  44. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  45. 2026-08-09 19:17 UTCEG score recompute
  46. 2026-08-09 19:17 UTCVendor advisory
  47. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  49. 2026-08-08 00:14 UTCEG score recompute
  50. 2026-08-08 00:14 UTCVendor advisory
  51. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  52. 2026-08-06 05:28 UTCEG score recompute
  53. 2026-08-06 05:28 UTCVendor advisory
  54. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  55. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  56. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  57. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  58. 2026-08-02 22:54 UTCEG score recompute
  59. 2026-08-02 22:54 UTCVendor advisory
  60. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  61. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  62. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  63. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  64. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  65. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  66. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  67. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-07-23 09:49 UTCOSV refresh
  69. 2026-07-23 03:07 UTCEG score recompute▼ 2.90
  70. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  71. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.2% · 14th percentile

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

Frequently asked(5)

What is CVE-2026-23950?
CVE-2026-23950 is a medium-severity vulnerability; its CVE record was published on January 20, 2026. node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the path-reservations system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has…
When was the CVE record for CVE-2026-23950 published?
The CVE record for CVE-2026-23950 was published on January 20, 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 1, 2026; the record at its source may have been updated since.
Is CVE-2026-23950 actively exploited?
CVE-2026-23950 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23950?
CVE-2026-23950 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-23950?
A fix for CVE-2026-23950 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23950 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-23950

Explore →

Is Your Infrastructure Affected by CVE-2026-23950?

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

Book a Demo →Browse All CVEs