CVE-2026-24001

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.6% (49th 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

Also known asEUVD-2026-2424 (ENISA EUVD) · GHSA-73rr-hh4g-fpgx (GitHub Security Advisories)Source: ENISA EUVD

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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

jsdiff is a JavaScript text differencing implementation. Prior to versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1, attempting to parse a patch whose filename headers contain the line break characters \r, \u2028, or \u2029 can cause the parsePatch method to enter an infinite loop. It then consumes memory without limit until the process crashes due to running out of memory. Applications are therefore likely to be vulnerable to a denial-of-service attack if they call parsePatch with a user-provided patch as input. A large payload is not needed to trigger the vulnerability, so size limits on user input do not provide any protection. Furthermore, some applications may be vulnerable even when calling parsePatch on a patch generated by the application itself if the user is nonetheless able to control the filename headers (e.g. by directly providing the filenames of the files to be diffed). The applyPatch method is similarly affected if (and only if) called with a string representation of a patch as an argument, since under the hood it parses that string using parsePatch. Other methods of the library are unaffected. Finally, a second and lesser interdependent bug - a ReDOS - also exhibits when those same line break characters are present in a patch's *patch* header (also known as its "leading garbage"). A maliciously-crafted patch header of length *n* can take parsePatch O(*n*³) time to parse. Versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1 contain a fix. As a workaround, do not attempt to parse patches that contain any of these characters: \r, \u2028, or \u2029.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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 none (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.

The score's inputs: 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

January 22, 2026

Last Modified

July 15, 2026

Advisory Details (7)

Auto-updated Jul 2, 2026
Patch available. Sources: github_pr, github, redhat, github_commit.
Red Hat

2431930 – (CVE-2026-24001) CVE-2026-24001 jsdiff: denial of service vulnerability in parsePatch and applyPatch

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-24001
GitHub advisoryMentions a patch (unverified)

Denial of Service vulnerability in parsePatch and applyPatch · Advisory · kpdecker/jsdiff · GitHub

Affected: v8.0.3.

https://github.com/kpdecker/jsdiff/security/advisories/GHSA-73rr-hh4g-fpgx
GitHub pull request

Fix the second denial-of-service vulnerability in parsePatch

Fix merged in kpdecker/jsdiff PR #649 on 2026-01-07 — awaiting tagged release

https://github.com/kpdecker/jsdiff/pull/649
Web page

Backport GHSA-73rr-hh4g-fpgx fix to v4 · Issue #653 · kpdecker/jsdiff · GitHub

https://github.com/kpdecker/jsdiff/issues/653
GitHub commit

commit 15a158523074 (kpdecker/jsdiff)

Fix landed in kpdecker/jsdiff commit 15a158523074 — awaiting tagged release

https://github.com/kpdecker/jsdiff/commit/15a1585230748c8ae6f8274c202e0c87309142f5

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmdiff @ 8.0.3 (fixes >= 6.0.0, < 8.0.3)—ghsa
npmdiff @ 5.2.2 (fixes >= 5.0.0, < 5.2.2)—ghsa
npmdiff @ 4.0.4 (fixes >= 4.0.0, < 4.0.4)—ghsa
npmdiff @ 3.5.1 (fixes < 3.5.1)—ghsa

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-diff4.0.2~dfsg-2 ... 8.0.3~dfsg-4 (14 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-diff5.0.0~dfsg+~5.0.1-4 ... 8.0.4~dfsg-3 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-diff5.0.0~dfsg+~5.0.1-4 ... 8.0.4~dfsg-3 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-diff5.0.0~dfsg+~5.0.1-4, 5.0.0~dfsg+~5.0.1-5, 5.0.0~dfsg+~5.0.1-6
  • every version up to 5.2.2~dfsg+~5.2.3-1: fixed in 5.2.2~dfsg+~5.2.3-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
diff—
  • 6.0.0 up to 8.0.3: fixed in 8.0.3
  • 5.0.0 up to 5.2.2: fixed in 5.2.2
  • 4.0.0 up to 4.0.4: fixed in 4.0.4
  • every version up to 3.5.1: fixed in 3.5.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 210 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 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-24001?
CVE-2026-24001 is a high-severity vulnerability; its CVE record was published on January 22, 2026. jsdiff is a JavaScript text differencing implementation. Prior to versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1, attempting to parse a patch whose filename headers contain the line break characters \r, \u2028, or \u2029 can cause the parsePatch method to enter an infinite loop. It then consumes memory…
When was the CVE record for CVE-2026-24001 published?
The CVE record for CVE-2026-24001 was published on January 22, 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-24001 actively exploited?
CVE-2026-24001 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-24001?
CVE-2026-24001 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-24001?
A fix for CVE-2026-24001 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-24001

Explore →

Is Your Infrastructure Affected by CVE-2026-24001?

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